4 ms·

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 standard

by pxc 1y ago

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 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096790 Maybe such changes are more substantial than the typical differences between GCC releases?

yjftsjthsd-h 1y ago
Surely if that's all they would just build with an explicit -std=whatever setting?
- opello 1y ago
  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://github.com/bpftrace/bpftrace/pull/3407 https://gcc.gnu.org/pipermail/gcc-patches/2024-August/659176.html 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-changes https://gcc.gnu.org/gcc-15/porting_to.html#header-dep-change...
  - opello 1y ago
    Just closing some tabs and followed this trail a bit further, it looks like guix fixed the issue too: https://codeberg.org/guix/guix/commit/7b66b41ce5cee48b14eb6cce3bb4b26f5b058652 https://codeberg.org/guix/guix/commit/7b66b41ce5cee48b14eb6c...
  - cozzyd 1y ago
    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.
    - yjftsjthsd-h 1y ago
      That seems like kicking the can down the road in a way that's worse in the long run IMHO
    - Ashymad 1y ago
      Isn't the --include option basically that?
      - cozzyd 1y ago
        Ah, you learn something new everyday, thanks!
    - ForOldHack 1y ago
      Isn't that what AI/Vibe coding is for? ( I am kidding a lot)(Ducking thrown paper balls)
vincent-manis 1y ago
I recently custom-built Guile for my Arch system, and found that it won't build with GCC 15, but will with 14, which is the only other version in the Arch repository. I think that the Guile maintainers will need to get busy fixing the incompatibilities in question, before GCC 16 appears.

by pxc 1y ago

yjftsjthsd-h 1y ago

Surely if that's all they would just build with an explicit -std=whatever setting?

opello 1y ago
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://github.com/bpftrace/bpftrace/pull/3407 https://gcc.gnu.org/pipermail/gcc-patches/2024-August/659176.html 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-changes https://gcc.gnu.org/gcc-15/porting_to.html#header-dep-change...
- opello 1y ago
  Just closing some tabs and followed this trail a bit further, it looks like guix fixed the issue too: https://codeberg.org/guix/guix/commit/7b66b41ce5cee48b14eb6cce3bb4b26f5b058652 https://codeberg.org/guix/guix/commit/7b66b41ce5cee48b14eb6c...
- cozzyd 1y ago
  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.
  - yjftsjthsd-h 1y ago
    That seems like kicking the can down the road in a way that's worse in the long run IMHO
  - Ashymad 1y ago
    Isn't the --include option basically that?
    - cozzyd 1y ago
      Ah, you learn something new everyday, thanks!
  - ForOldHack 1y ago
    Isn't that what AI/Vibe coding is for? ( I am kidding a lot)(Ducking thrown paper balls)

vincent-manis 1y ago

I recently custom-built Guile for my Arch system, and found that it won't build with GCC 15, but will with 14, which is the only other version in the Arch repository. I think that the Guile maintainers will need to get busy fixing the incompatibilities in question, before GCC 16 appears.