Just to give you an idea of how much software GCC 14's default of -Werror=implicit-function-declaration breaks, here are two pkgsrc bulk build results:

GCC 13.3.0: 24835/28450
GCC 14.3.0: 2589/28450

reports.pkgci.org/SmartOS/upst…

reports.pkgci.org/SmartOS/upst…

I also had to fix up a bunch of things before the build would even start.

This could take a while. And then the fun starts all over again with GCC 15's changes...

#pkgsrc #c

#c #pkgsrc
in reply to Jonathan Perkin

One of the more insidious fallouts from GCC 14 changes are in configure scripts.

For example, today I've been debugging why tcl's floating point support was broken.

Turns out its configure script test for whether the system is big endian was now failing due to exit() not being declared, and the compile test failure was being interpreted as amd64 suddenly becoming big endian.

I get it, you don't like Rust becoming popular, but breaking existing software in weird and wonderful ways is NOT OK.