←back to thread

137 points 6581 | 2 comments | | HN request time: 0s | source
Show context
yjftsjthsd-h ◴[] No.45105621[source]
> For example, he has had to maintain various Guile dependencies, and deal with the fact that Guix uses ""fairly old"" GCC versions whereas Debian usually ships the latest GCC version available for a given release.

It's odd that guix is both rolling release but also uses older GCC versions; usually I'd expect those from very different cultures.

replies(1): >>45106091 #
pxc ◴[] No.45106091[source]
It seems that it doesn't build with releases of GCC from April 2025 onward, at least with default settings, because it doesn't build with the C23/C++23 standards.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096790

Maybe such changes are more substantial than the typical differences between GCC releases?

replies(2): >>45106414 #>>45108639 #
yjftsjthsd-h ◴[] No.45106414[source]
Surely if that's all they would just build with an explicit -std=whatever setting?
replies(1): >>45107125 #
opello ◴[] No.45107125{3}[source]
Looking at the build log in the linked Debian issue, there is an argument setting -std=c++11. It seems as though an implicit inclusion of <cstdint> had been provided by libstdc++ in the past and was removed as of GCC 15.

https://github.com/bpftrace/bpftrace/pull/3407

https://gcc.gnu.org/pipermail/gcc-patches/2024-August/659176...

Looks like they did in fact add the header detail to the porting guide:

https://gcc.gnu.org/gcc-15/porting_to.html#header-dep-change...

replies(2): >>45109181 #>>45111953 #
cozzyd ◴[] No.45111953{4}[source]
it would be nice if g++ had an --implicit-includes=[foo,bar] option that would make it easier for a distro to shotgun fix such incompatibilities with CXXFLAGS rather than doing real work.
replies(3): >>45112157 #>>45113137 #>>45117965 #
1. Ashymad ◴[] No.45113137{5}[source]
Isn't the --include option basically that?
replies(1): >>45115975 #
2. cozzyd ◴[] No.45115975[source]
Ah, you learn something new everyday, thanks!