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.
<snip>... Even 14.2 cannot compile a 4.19 kernel anymore.<snip>...
I've been building 4.19 kernels on 14.2 for over two months without any issues. Still using the GCC 5.5. I'm not sure why you are stating that 4.19 can't be built or implying that the security backports in any kernel release are dependent on GCC version? I haven't found anything on LQ or in Kernel blogs that say you must be using a specific GCC to build the kernel. I'm ready to be corrected, but it just doesn't match my experience. Cheers
I don't know, I have a feeling that things are getting rather close though. If left longer than two weeks it will be the longest gap between releases ever. PV has been rather quiet of late [and Eric, for that matter], and no new kernel on stable for nearly four months. Of course none of these things by themselves indicate much, but just call it a hunch. Of course I am happy [and privileged] to wait as long as the man wants, but I have an inkling that we're nearly there.
I hope you're right about Slack 15 getting close, but I'd advise to not hold your breath, there are still frequent issues with -current popping up here in the forum and it doesn't look like there's a conclusion about the default desktop env. for X yet, nor about KDE's future.
I hope PV is doing fine, had a wonderful holidays season and enjoying now some home-brewed beer with AlienBoB in the "US of A": https://alien.slackbook.org/blog/kde...-year-edition/
"But, I get to visit the US of A in January, just booked the flights and hotels today. "
I guess we should focus on the kernels in this kernel related thread, I fear cwizardone will report us for hijacking his rather useful thread
I've been building 4.19 kernels on 14.2 for over two months without any issues. Still using the GCC 5.5.
I admit I haven't been compiling kernels recently, so that part was wrong.
But DO note this part of the 14.2 ChangeLog
Quote:
Please note that this kernel was compiled with gcc-5.5.0, also provided as an update for Slackware 14.2. You'll need to install the updated gcc in order to compile kernel modules that will load into this updated kernel.
so gcc 5.5 was already an update as the prevous version of the compiler set couldn't compile the kernel anymore (nor modules FOR it).
The original gcc as distributed with the 14.2 release was 5.3
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,154
Original Poster
Rep:
Quote:
Originally Posted by abga
I hope you're right about Slack 15 getting close, but I'd advise to not hold your breath, there are still frequent issues with -current popping up here in the forum and it doesn't look like there's a conclusion about the default desktop env. for X yet, nor about KDE's future.
I hope PV is doing fine, had a wonderful holidays season and enjoying now some home-brewed beer with AlienBoB in the "US of A": https://alien.slackbook.org/blog/kde...-year-edition/
"But, I get to visit the US of A in January, just booked the flights and hotels today. "
I guess we should focus on the kernels in this kernel related thread, I fear cwizardone will report us for hijacking his rather useful thread
Oh, I agree, but the hardware manufacturers are not sitting around waiting for Slackware. Hopefully, we will see a new release in the very near future.
Last edited by cwizardone; 01-12-2019 at 07:50 AM.
so gcc 5.5 was already an update as the prevous version of the compiler set couldn't compile the kernel anymore (nor modules FOR it).
The original gcc as distributed with the 14.2 release was 5.3
As far as I know, it can compile it, just not with the retpoline fixes enabled. I was able to build earlier 4.19 kernels (up to 4.19.5) with the older gcc 5.3, but when I tried building a newer one (I can't remember what version), it complained it couldn't because of retpoline being enabled in the kernel. I think with earlier 4.19 versions, it would just ignore the retpoline if the compiler couldn't handle it, but newer ones made it error out.
From: Linus Torvalds
Date: Sun Jan 13 2019 - 18:10:19 EST
So the merge window had somewhat unusual timing with the holidays, and
I was afraid that would affect stragglers in rc2, but honestly, that
doesn't seem to have happened much. rc2 looks pretty normal.
Were there some missing commits that missed the merge window? Yes. But
no more than usual. Things look pretty normal.
What's a bit abnormal is that I'm traveling again, and so for me it's
a Monday release, but it's (intentionally) the usual "Sunday
afternoon" release schedule back home. I'm trying to not surprise
people too much.
As to actual changes: all looks fairly normal. Yes, there's a fair
number of perf tooling updates, so that certainly stands out in the
diffstat, but if you ignore the tooling and just look at the kernel,
it's about two thirds drivers (networking, gpu, block, scsi..), with
the rest being the usual mix of arch updates (ARM, RISC-V, x86, csky),
with some filesystem (btrfs, cifs) and vm fixes.
Mr. Torvalds' announcement, posted at 03:26:31 EST Monday morning:
Quote:
Linux 5.0-rc3
From: Linus Torvalds
Date: Mon Jan 21 2019 - 03:26:31 EST
I'm keeping to the usual "Sunday afternoon on the US west coast"
release schedule, even if it's actually already Monday afternoon in
here New Zealand. I'm traveling for LCA 2019.
This rc is a bit bigger than usual. Partly because I missed a
networking pull request for rc2, and as a result rc3 now contains
_two_ networking pull updates. But part of it may also just be that it
took a while for people to find and then fix bugs after the holiday
season.
So we have more commits than usual for rc3, although certainly not
breaking any records. And things look fairly normal, except that the
diffs are unusually big in the tooling department, with lots of bpf
test additions.
On the "kernel proper" side, things look fairly normal, although with
the above caveat that we have two weeks worth of networking fixes, and
that shows up as both core networking and network driver updates.
But we've got other driver updates too (gpu, rdma, scsi, crypto,
acpi..) some arch updates (mainly some mips fixes), and various
smaller filesystem fixes.
The appended shortlog gives an overview of the details for people who
want to quickly just scroll down the kinds of things that got fixed.
Nothing particularly odd strikes me.
Linus
---
Last edited by cwizardone; 01-21-2019 at 07:03 AM.
Is there a reason why DUSK does not ship also packages for the 4.20 kernels?
TBH, I would like to try the well made DUSK kernels on 4.20 versions.
Eventually, if someone here can suggest me a good config for the 4.20 kernels, would be greatly appreciated.
I just start off with the .config from the stock Slackware kernel do a make oldconfig and then trim the fat off by deselecting the stuff I do not need and making any driver that isn't required to boot that can be a module a module in menuconfig.
Last edited by Pixxt; 01-23-2019 at 06:25 AM.
Reason: edit
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.