Re: git: 40478d7acd2a - main - biology/bifrost: Unbreak build on 15-CURRENT

On Mon, 26 May 2025, Jason Bacon wrote:
>>> (USE_GCC itself is not problematic, especially if something really is
>>> GCC-specific. Just using it to work around clang getting stricter over
>>> time has often bitten us with loads of extra work and delays when then
>>> updating GCC_DEFAULT.)
>> Maybe try "USES=llvm:max=18" as a workaround?
> I would consider that if it proved difficult to fix for the base 
> compiler, but I'd hate to have a compiler dependency if we can avoid it.

Agreed. This is why I raised USE_GCC being such a compiler dependency, 
where I'd prefer USES=llvm:max=18 over USE_GCC=yes which causes those 
problems down the path when upgrading GCC_DEFAULt.

On Tue, 27 May 2025, Jason Bacon wrote:
> Updated bifrost and kallisto are committed.

Very nice, thank you! Especially for thinking of the other port as well.

> Hayzam came up with a DataStorage.tcc fix, and later found the same 
> suggestion here:
> 
> https://github.com/pmelsted/bifrost/pull/18/files

Nice.

Looks like both our ports tree improved and upstream hopefully also will 
pick up that fix.

Gerald