4 ms·
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 pr
by 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 agoJust 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 agoit 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 agoThat seems like kicking the can down the road in a way that's worse in the long run IMHO
- Ashymad 1y agoIsn't the --include option basically that?
- cozzyd 1y agoAh, you learn something new everyday, thanks!
- ForOldHack 1y agoIsn't that what AI/Vibe coding is for? ( I am kidding a lot)(Ducking thrown paper balls)