Caveat for ugrading gcc in a distribution based on Slackware-14.2?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have gcc version 5.5.0 (genuine Slackware package).
If upgrading to the version in -current (10.2.0) or at least 9.2.0, will I have rebuild libtool after that ?
According to gentoo I would need to also rebuild llvm, clang and wxGTK3 (installed in Slint). Others that come to mind?
On the other hand, do I need to first upgrade other components of the system before upgrading gcc?
Thanks for any clue.
PS The reason I consider upgrading is that some software need or will soon need a more recent GCC
I suppose you will recompile gcc. If so I don't think you need to upgrade any other libraries. I have already compile gcc form scratch for cross-compilers and you can have a new gcc and (very) old libs (even glibc).
For other packages which were compiled with another version of gcc, the libs libgcc_s.so libstdc++.so of that version should be kept alongside the new ones.
Thanks. Indeed will I recompile (I do that already for the kernels). That means that I will need to also rebuild aaa_elflibs that also ships these libraries. And I will of course keep the /usr/lib64/*.la files else a lot of installed software will become unhappy.
Last edited by Didier Spaier; 02-25-2021 at 08:21 AM.
Reason: s/-/_/
% Add GCC to PATH
if contains(ver_str, 'R2016b') || contains(ver_str, 'R2017a') || ...
contains(ver_str, 'R2017b')
if exist('/opt/gcc-4.9.4/bin', 'dir')
setenv('PATH', ['/opt/gcc-4.9.4/bin:' getenv('PATH')]);
end
end
if contains(ver_str, 'R2018a') || contains(ver_str, 'R2018b') || ...
contains(ver_str, 'R2019a') || contains(ver_str, 'R2019b') || ...
contains(ver_str, 'R2020a')
if exist('/opt/gcc-6.3.0/bin', 'dir')
setenv('PATH', ['/opt/gcc-6.3.0/bin:' getenv('PATH')]);
end
end
if contains(ver_str, 'R2020b')
if exist('/opt/gcc-8.4.0/bin', 'dir')
setenv('PATH', ['/opt/gcc-8.4.0/bin:' getenv('PATH')]);
end
end
So when compiling things in MATLAB it will automagically pick up the correct GCC version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.