At Sun, 19 Oct 2025 16:00:11 -0400, Andrew Cagney <andrew.cagney%gmail.com@localhost> wrote: Subject: Re: Fixing configure failures from newer gcc > > On Sun, 19 Oct 2025 at 13:17, Greg Troxel <gdt%lexort.com@localhost> wrote: > > > > It's not local policy. > > But -std is being discussed as a local pkgsrc policy. Hmmm.... I agree calling it a "policy" might be a stretch. Use of "-std=" is a workaround for the fallout of various platforms having switched to compilers that default to wanting to build for gnu23 when most code is still only compatible with gnu17 at best, maybe only gnu99. Something that might be called a "policy" could be to install an older compiler for those platforms, but that's a headache for some platforms, so sticking to the host native compiler means having to do workarounds. > I think a more reasonable expectation is that a package be buildable > with the default settings of mainstream compilers less than 5 years > old (i.e., LTS). I think that's a CLM! At least from a pkgsrc point of view. It's certainly not the current state of affairs. > While buildable with c23, the package still needs > to wait a few years before adopting c23 features (like bool being > defined). Sure, but that's a separate issue -- it only means that the package _also_ remain buildable with compilers more than 5 years old. -- 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:
pgpHLvEkAaMyC.pgp
Description: OpenPGP Digital Signature