Re: Fixing configure failures from newer gcc

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2025-10-11 at 14:00 BST, Greg Troxel wrote:

> It's also possible that gcc14 is defaulting to some new c std, and this
> program simply isn't in that standard.  I think that's also broken of
> gcc

What's happening is that many things that were previously warnings are 
now errors:

  https://gcc.gnu.org/gcc-14/porting_to.html

and 15 may make it even worse:

  https://gcc.gnu.org/gcc-15/porting_to.html

I've been posting daily bulk builds of GCC 14 builds for a few months 
now and after fixing up a bunch of initial breakage where there were 
tens of thousands of broken packages there is still a lot, and there 
will be a very long tail due to the amount of historical software we 
ship.

Whether it's broken or not depends on your point of view.  It's good 
that they are trying to enforce correctness, but breaking software that 
previously built fine and worked fine for the most part in the default 
compilation environment is pretty shitty behaviour, and should IMHO only 
have been done for software that explicitly requested newer standards.

I just don't think there are many other projects out there like us that 
are continuing to build old software with newer compilers, and so this 
doesn't affect them.

Personally, while I'm doing the daily builds on GCC 14, I'm going to be 
sticking to 13 for my release builds for as long as possible because 
this is going to be messy for a while.  In the meantime we'll try to fix 
up as many issues as possible.  It certainly helps that some of the 
Linux distributions are getting bitten by this now so the pool of people 
working on it is larger.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com