Re: lang/rust/Makefile for 1.82.0 has wrong llvm:min= value [I got that incorrect]; more

Mark Millard wrote:
> On Nov 14, 2024, at 19:30, Tatsuki Makino <tatsuki_makino@hotmail.com> wrote:
> 
>> Since option PORT_LLVM is not turned on in the official version, it seems that there is no problem with using of the bundle llvm.
>> However, if we want to use llvm instead of a bundle on an architecture where the compiler causes problems, that version is no longer supported and we need to rewrite the version number there.
>>
>> … Is that what you mean? :)
> 
> When I got into this area it was because someone on discord was getting
> errors like:
> 
> ld.lld: error: ../../../x86_64-unknown-freebsd/release/libgkrust.a(ews_xpcom-da5573b2cf91b84e.ews_xpcom.c68a27d7391ba4aa-cgu.0.rcgu.o): Unknown attribute kind (91) (Producer: 'LLVM19.1.1-rust-1.82.0-stable' Reader: 'LLVM 17.0.6') clang++: error: linker command failed with exit code 1 (use -v to see invocation)
> 
This looks like an LTO interaction between two different LLVM bitcode 
versions, which along with the rest of LLVM, do not guarantee 
compatibility. It goes without saying that the LTO option in gecko@ 
ports should only be enabled when the LLVM version matches across the 
clang (gecko@ ports force devel/llvm*) and Rust bits. With LTO disabled 
this is moot.

-- 
Charlie Li
...nope, still don't have an exit line.