Date: Tue, 30 Jul 2024 21:00:59 -0500 From: Larry Rosenman <ler@lerctr.org> To: Ed Maste <emaste@freebsd.org> Cc: Freebsd current <freebsd-current@freebsd.org> Subject: Re: build failure: clang.full Message-ID: <f21438fcaefb1e26d3ce9a6094337b78@lerctr.org> In-Reply-To: <762cd65e1cb2b2c138e3174d9787e135@lerctr.org> References: <fcddcb144c146e8a7aebd8098e79f008@lerctr.org> <CAPyFy2Dtpq4c14s7kRNtjpJ2XTi_t0HytWsPzT=v8Z5priCgLg@mail.gmail.com> <762cd65e1cb2b2c138e3174d9787e135@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/30/2024 9:25 am, Larry Rosenman wrote: > On 07/30/2024 9:22 am, Ed Maste wrote: >> On Mon, 29 Jul 2024 at 19:54, Larry Rosenman <ler@lerctr.org> wrote: >>> >>> I'm getting the following on an up2date checkout: >>> Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full >>> ld: warning: >>> /usr/obj/usr/src/amd64.amd64/lib/clang/libllvm/libllvm.a: >>> archive member 'FaultMaps.o' is neither ET_REL nor LLVM bitcode >> >> This looks like you have a corrupt object in this archive. If you want >> to start on the path of determining the root cause you could try >> extracting FaultMaps.o (using ar or tar) and seeing what file(1) says >> about it. > This happens even with a FRESH (I.E. empty) /usr/obj. It apparently got fixed, I just made it through a buildworld/buildkernel. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f21438fcaefb1e26d3ce9a6094337b78>