Re: C++20 and gcc12/10

[David Holland <dholland-pkgtech%netbsd.org@localhost>]

On Sun, Apr 06, 2025 at 07:28:29PM +0200, Havard Eidnes wrote:
 > > No, this belongs in infrastructure.  A package should only have to
 > > declare what it needs in terms of compiler support, not have
 > > OS-specific hacks spread across them.  Since adding support for
 > > *_FEATURES there shouldn't be any GCC_REQD in packages.
 > 
 > Well.
 > 
 > What to do when "older" GCCs do not produce a working result?
 > Such as e.g. gcc < 12 fails to build a working LLVM 18.x as part
 > of the rust package on sparc64?  That's sort of hard to express
 > using the *_FEATURES settings.

Dealing with compiler bugs is not the same as dealing with language
dialects. Seems like there are two basic choices: GCC_REQD, or
checking the compiler version and adding "this GCC can't compile this
package" to PKG_FAIL_REASON.

The latter's perhaps better, though.

-- 
David A. Holland
dholland%netbsd.org@localhost