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.
Maybe you have accidentally installed -current packages to your 14.2 system. Which gcc version do you have? It should be 5.3.0 in 14.2. 'gcc -v' will tell the version. It's linked against libmpfr.so.4, while gcc 7.2.0 in -current is linked against libmpfr.so.6.
Maybe you have accidentally installed -current packages to your 14.2 system. Which gcc version do you have? It should be 5.3.0 in 14.2. 'gcc -v' will tell the version. It's linked against libmpfr.so.4, while gcc 7.2.0 in -current is linked against libmpfr.so.6.
Very interesting because I do indeed have 7.2.0... how did that happen? I've done nothing (intentionally anyways) to pull this version, I just do my usual slackpkg install-new && slackpkg upgrade-all when I get an email regarding security patches from that Slackware mailing list. I tried a slackpkg reinstall gcc but it's still on 7.2.0
Very interesting because I do indeed have 7.2.0... how did that happen? I've done nothing (intentionally anyways) to pull this version, I just do my usual slackpkg install-new && slackpkg upgrade-all when I get an email regarding security patches from that Slackware mailing list. I tried a slackpkg reinstall gcc but it's still on 7.2.0
This is likely because you have your slackpkg mirror set to -current rather than 14.2. Depending on how you've handled the upgrade-all/install-new, you may be running the full development version of Slackware.
Very interesting because I do indeed have 7.2.0... how did that happen? I've done nothing (intentionally anyways) to pull this version, I just do my usual slackpkg install-new && slackpkg upgrade-all when I get an email regarding security patches from that Slackware mailing list. I tried a slackpkg reinstall gcc but it's still on 7.2.0
Some might say that one courts abdication of "intentionally so" as soon as we rely on automation. At the very least it seems we should pay close attention to the rules we do specify that govern that automation. We need to be very thoughtful when we consider the axiom that "convenience can lead to weakness".
More to the immediate point I hope the driver install is now working properly. It seems it is. Congratulations for good sleuthing and tenacity.
This is likely because you have your slackpkg mirror set to -current rather than 14.2. Depending on how you've handled the upgrade-all/install-new, you may be running the full development version of Slackware.
So I did check /etc/slackpkg/mirrors but didn't think to check /etc/slackpkg/slackpkgplus.conf as I installed slackpkgplus when I installed multilib... I uncommented the wrong mirror in that one. I just flipped it back to 14.2 and running slackpkg again to see if it rolls it back to gcc-5.3.0. If not I should be able to figure it out manually (I hope)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.