As you can see I haven't managed to pull off a linux-7 yet but have
managed to upgrade to gcc-16.1.0. One step at a time.
I haven't noticed anything all that exciting that pertains to me
from linux-6 to Linux-7 yet, so there's that.
What are some notable changes in the new gcc? I haven't read
anything yet, so feel free to enlighten me. ;)
kernel headers is what has me stalled at the moment. I can upgrade
to linux-7.0.3 as long as I keep the linux-6.18.26 headers in play.
At the moment I have no enlightenment other than the kernel headers
issue which I am sure will be resolved real soon. I am guessing
patching glibc-2.43 or using the latest glibc-2.43.9000 will provide
some insight. That will likely be my next attempt sometime in the
near future (days). Then I might have some real enlightenment
instead of conjecture or what little I've read about it as of this
writing. Bottomline is that gcc-16 will soon become a staple
compiler taking over from gcc-15. It is the natural order of things
along with glibc and the linux kernel. I call it synchronicity.
That's my story and I am sticking to it ... until a better story
presents itself.
Is it just me or do kernel releases seem to be happening quite a bit
faster these days?
I meant more in the lines of c++26 on it's way to make us have to
update a lot of old code.
I don't mind stories, so long as they're interesting!
I meant more in the lines of c++26 on it's way to make us have to
update a lot of old code.
I am still a tad miffed about the above being a tad too quick.
I am still working on it. So far it hasn't been all that
interesting but it is very early on in this chapter of the book. I
am in no rush, how about you?
Linux version 7.0.3 (root@europoint) (gcc (GCC) 16.1.0, GNU ld (GNU
Binutils) 2.46.0.20260210) #1 SMP PREEMPT_DYNAMIC Sat May 2
23:22:09 UTC 2026
Groovy.
I just finished compiling everything I currently use, and then some
(xorg, firefox and the such), and so far only rdfind-1.8.0 required
a fix;
CXX="g++ -std=c++17" ./configure --prefix=/usr"
did the trick. Everything else is as before and no standards were
harmed in the making.
Everything else is as before and no standards were harmed in the
making.
The only time I feel the need to rush is when something breaks
Will "-std=c++17" always be an option?
but rather just maintaining old code so that it still compiles.
How great is that?
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 493853:24:37 |
| Calls: | 146 |
| Files: | 547 |
| D/L today: |
6 files (97K bytes) |
| Messages: | 76,985 |