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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
The new Nvidia 470.129.06 driver builds with the 5.18-rc7 kernel, but the most recent VirtualBox Test build does not. OTOH, the VirtualBox site is down at the moment so maybe something new will have been posted by the time it comes back online.
Last edited by cwizardone; 05-16-2022 at 11:46 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
Year 2022, Round 30.
Another batch of updates has been scheduled for release on Wednesday, 18 May 2022, at approximately 19:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Missed the warning probably, but LTS kernel 5.15.x no longer supports the compiler shipped in Slackware 14.2
Mine is now frozen at 5.15.29, which compiles fine on 14.2, so I guess it happened somewhere after that release.
5.15.29 on 32bit Slackware 14.2 with 32bit nvidia driver 390.151 works OK (but seems like EOL, because all the vulnerabilities).
5.15.41 compiles fine on clean 64bit Slackware 15.0 (no nvidia on that one).
FWIW I just booted into Slackware64-14.2 for the first time in a few weeks and compiled 5.17.9 no problem with gcc 5.5.0 multilib, python2 2.7.17, python3 3.7.2.
Last edited by Spidergawd; 05-19-2022 at 12:24 AM.
Reason: typo
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
The only requirement to build kernel is gcc. This means that even freshly installed Slackware 14.2 is good enough to build the latest kernels.
I did that few months ago. Just disable few options and all runs fine.
On updated 14.2 all will work when using default Slackware config for the latest kernel because offending option is disabled by default (related to xeon cpus).
Don't worry about it guys, it's probably just me being suspicious of everything.
All I know is that yesterday it was OK on 5.15.29, and when I tried to bump it to 5.15.41 the message was something like:
Code:
Sorry, this compiler is not supported.
Likely a test has failed, according to content of Kconfig.include
Since then I reverted it back to kernel-huge, compiled 5.15.29 again with same 5.15.29 config it used previously and it was OK again.
Today, I tried the same thing again and now 5.15.41 compiles fine, no longer complains about the compiler or anything like that.
Same config, same compiler, same everything. Never had python3 there, or rust, or any /d/ stuff that isn't part of Slackware 14.2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
