install different version of GCC side by side
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
My primary problem is in my Fedora 28, GCC8
is installed. Now, this gives libgfortran.so.5
.
But many of my applications are not updated and still depends on libgfortran.so.3
So, how can I solve the problem? Is it safe to ln libgf.so.5 to libgfso.3
?
fedora gcc shared-library fortran
add a comment |Â
up vote
2
down vote
favorite
My primary problem is in my Fedora 28, GCC8
is installed. Now, this gives libgfortran.so.5
.
But many of my applications are not updated and still depends on libgfortran.so.3
So, how can I solve the problem? Is it safe to ln libgf.so.5 to libgfso.3
?
fedora gcc shared-library fortran
You can install as many different versions ofgcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.
â Nasir Riley
Sep 11 at 13:29
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
My primary problem is in my Fedora 28, GCC8
is installed. Now, this gives libgfortran.so.5
.
But many of my applications are not updated and still depends on libgfortran.so.3
So, how can I solve the problem? Is it safe to ln libgf.so.5 to libgfso.3
?
fedora gcc shared-library fortran
My primary problem is in my Fedora 28, GCC8
is installed. Now, this gives libgfortran.so.5
.
But many of my applications are not updated and still depends on libgfortran.so.3
So, how can I solve the problem? Is it safe to ln libgf.so.5 to libgfso.3
?
fedora gcc shared-library fortran
fedora gcc shared-library fortran
edited Sep 11 at 2:23
Jeff Schaller
33.1k849111
33.1k849111
asked Sep 11 at 1:28
BaRud
5332715
5332715
You can install as many different versions ofgcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.
â Nasir Riley
Sep 11 at 13:29
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday
add a comment |Â
You can install as many different versions ofgcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.
â Nasir Riley
Sep 11 at 13:29
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday
You can install as many different versions of
gcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.â Nasir Riley
Sep 11 at 13:29
You can install as many different versions of
gcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.â Nasir Riley
Sep 11 at 13:29
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
Linking the newer version to the older one probably won't work, because that number change usually reflects an ABI change.
The best approach for this is to run your older applications in containers â in this case, CentOS 7 has the version of libgfortran you are looking for, so a CentOS 7 container should provide you forward compatibility for a good long time.
He can give it a try. Worst case, it just won't work. The newer version of libraries such aslibgfortran
andlibstdc++
are normally backwards compatible. I create symlinks of older versions all the time.
â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version ofgcc
with different libraries.
â Nasir Riley
Sep 11 at 15:32
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Linking the newer version to the older one probably won't work, because that number change usually reflects an ABI change.
The best approach for this is to run your older applications in containers â in this case, CentOS 7 has the version of libgfortran you are looking for, so a CentOS 7 container should provide you forward compatibility for a good long time.
He can give it a try. Worst case, it just won't work. The newer version of libraries such aslibgfortran
andlibstdc++
are normally backwards compatible. I create symlinks of older versions all the time.
â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version ofgcc
with different libraries.
â Nasir Riley
Sep 11 at 15:32
add a comment |Â
up vote
2
down vote
Linking the newer version to the older one probably won't work, because that number change usually reflects an ABI change.
The best approach for this is to run your older applications in containers â in this case, CentOS 7 has the version of libgfortran you are looking for, so a CentOS 7 container should provide you forward compatibility for a good long time.
He can give it a try. Worst case, it just won't work. The newer version of libraries such aslibgfortran
andlibstdc++
are normally backwards compatible. I create symlinks of older versions all the time.
â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version ofgcc
with different libraries.
â Nasir Riley
Sep 11 at 15:32
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Linking the newer version to the older one probably won't work, because that number change usually reflects an ABI change.
The best approach for this is to run your older applications in containers â in this case, CentOS 7 has the version of libgfortran you are looking for, so a CentOS 7 container should provide you forward compatibility for a good long time.
Linking the newer version to the older one probably won't work, because that number change usually reflects an ABI change.
The best approach for this is to run your older applications in containers â in this case, CentOS 7 has the version of libgfortran you are looking for, so a CentOS 7 container should provide you forward compatibility for a good long time.
answered Sep 11 at 13:13
mattdm
27.2k1170109
27.2k1170109
He can give it a try. Worst case, it just won't work. The newer version of libraries such aslibgfortran
andlibstdc++
are normally backwards compatible. I create symlinks of older versions all the time.
â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version ofgcc
with different libraries.
â Nasir Riley
Sep 11 at 15:32
add a comment |Â
He can give it a try. Worst case, it just won't work. The newer version of libraries such aslibgfortran
andlibstdc++
are normally backwards compatible. I create symlinks of older versions all the time.
â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version ofgcc
with different libraries.
â Nasir Riley
Sep 11 at 15:32
He can give it a try. Worst case, it just won't work. The newer version of libraries such as
libgfortran
and libstdc++
are normally backwards compatible. I create symlinks of older versions all the time.â Nasir Riley
Sep 11 at 13:22
He can give it a try. Worst case, it just won't work. The newer version of libraries such as
libgfortran
and libstdc++
are normally backwards compatible. I create symlinks of older versions all the time.â Nasir Riley
Sep 11 at 13:22
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
@NasirRiley Eh, worst case it'll appear to work but then crash unexpectedly at a bad time.
â mattdm
Sep 11 at 13:23
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version of
gcc
with different libraries.â Nasir Riley
Sep 11 at 15:32
That can indeed happen if there's something that's no longer supported or if it's built against something that requires something that's no longer supported. It's up to him to decided. If he just doesn't know then it's better that he just run it in a container as you've suggested where he can install a different version of
gcc
with different libraries.â Nasir Riley
Sep 11 at 15:32
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468146%2finstall-different-version-of-gcc-side-by-side%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You can install as many different versions of
gcc
as you want. The only thing that might come up is that you'll constantly have to change which ones you're using for different applications.â Nasir Riley
Sep 11 at 13:29
A workaround could be using Nix ( nixos.org/nix ) to manage the user specific programs.
â Mioriin
yesterday