At Mon, 20 Oct 2025 05:26:21 +1100, matthew green <mrg%eterna23.net@localhost> wrote: Subject: re: Fixing configure failures from newer gcc > > the problem with the "use -std=" advice is that it does not help the > new problems GCC 14 is turning into error cases. I'm pretty sure it does actually. Indeed the GCC-14 documentation says so: Turning errors back into warnings Sources that cannot be ported to standard C can be compiled with -fpermissive, -std=gnu89, or -std=c89. https://gcc.gnu.org/gcc-14/porting_to.html#errors-as-warnings I haven't tried "-fpermissive", but I don't think it is as widely portable as "-std=". Clang accepts it, and hopefully does the same thing with it though it does not document it, so personally I would stick to "-std=". As you say though you have to make the right choice -- gnu99 is probably safest, though gnu17 might be generally OK. -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgprUaRKrkxXj.pgp
Description: OpenPGP Digital Signature