Date: Tue, 3 May 2022 12:56:23 -0400 From: Frank Seltzer <frank_s@bellsouth.net> To: Jan Beich <jbeich@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: Firefox 100.0_1,2 immediate crash on signal 5 Message-ID: <20220503125623.291f53d0@Ace.nina.org> In-Reply-To: <20220503113921.2878faad@Ace.nina.org> References: <20220503053032.3d8f89ea.ref@Ace.nina.org> <20220503053032.3d8f89ea@Ace.nina.org> <pmku-g30a-wny@FreeBSD.org> <20220503112956.0a457d7d@Ace.nina.org> <20220503113921.2878faad@Ace.nina.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 3 May 2022 11:39:21 -0400 Frank Seltzer <frank_s@bellsouth.net> wrote: > On Tue, 3 May 2022 11:29:56 -0400 > Frank Seltzer <frank_s@bellsouth.net> wrote: > > > On Tue, 03 May 2022 15:27:33 +0200 > > Jan Beich <jbeich@FreeBSD.org> wrote: > > > > > Try rebuilding without LTO. rust-1.60 emits LLVM 14 bytecode that > > > LLD from llvm13 may not understand. firefox cannot switch to > > > llvm14 yet due to missing wasi-compiler-rt14. In the past firefox > > > build usually broke due to LLVM mismatch, so quickly noticed > > > during exp-run. > > > > I have rust 1.60.0 and llvm13-13.0.1_2 installed. > > > > How do I build without LTO? > > > > OK, I found LTO. Compiling firefox even as we speak. Compile completed and firefox is back.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220503125623.291f53d0>