Date: Tue, 21 Jan 2025 11:33:30 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Andrea Venturoli <ml@netfence.it> Cc: "tagattie@freebsd.org" <tagattie@FreeBSD.org>, ports@freebsd.org Subject: Re: Cannot build devel/electron32 Message-ID: <6770C572-8449-4834-B3A5-690D5172F0A7@FreeBSD.org> In-Reply-To: <D71EDC64-076B-4924-BE1A-4A3B3BF69E3A@FreeBSD.org> References: <036b979a-6e73-4e52-a687-1624d2e1a549@netfence.it> <20CEC5EA-5F7C-476F-8145-E20F4F43821D@FreeBSD.org> <23404a49-3020-4123-8f52-6b447a89a06c@netfence.it> <D71EDC64-076B-4924-BE1A-4A3B3BF69E3A@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Jan 2025, at 11:11, Dimitry Andric <dim@FreeBSD.org> wrote: >=20 > On 21 Jan 2025, at 10:52, Andrea Venturoli <ml@netfence.it> wrote: >>=20 >> On 1/21/25 09:27, Dimitry Andric wrote: >>=20 >>> Every time this happens, something in the ports build is mixing up = llvm versions, while attempting to do LTO. That won't work. >>> In this case it looks like rust is built against llvm 19, while the = linker is lld 18. Hence switching to lld 19 fixes it. >>=20 >> Thought so, though I don't know why. >> I did not choose with LLVM to use for Rust: I guess 19 is the default = now? >=20 > If you are running 14.2-RELEASE your base system compiler and linker = are llvm 18, but for some reason rust (or electron) pulls in llvm 19. = Maybe it is the embedded copy of llvm in rust, I don't know. I just checked, the rust 1.83.0 port has an embedded copy of llvm = 19.1.1. So anything port that wants to do link time optimization against = rust object files, will have to use lld 19 to link. -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6770C572-8449-4834-B3A5-690D5172F0A7>