Date: Wed, 6 May 2026 07:50:30 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: ar: error: libclang.a: 'ParseDecl.o': section header table goes past EOF Message-ID: <aftVNo1vagUO9Xjs@www.zefox.net> In-Reply-To: <4fab914f-ff17-4312-a098-975b6c103e05@yahoo.com> References: <afoDUSr7xeYIeL64@www.zefox.net> <2c2ab68d-83eb-4b6d-996d-10c2169a2165@yahoo.com> <afqMIyNQGtJpRQGS@www.zefox.net> <4fab914f-ff17-4312-a098-975b6c103e05@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On Tue, May 05, 2026 at 09:59:02PM -0700, Mark Millard wrote: > On 5/5/26 17:32, bob prohaska wrote: > > On Tue, May 05, 2026 at 11:37:12AM -0700, Mark Millard wrote: > >> On 5/5/26 07:48, bob prohaska wrote: > >>> A Pi2B (armv7) is failing buildworld with: > >>> > >>> Building static clang library > >>> ar: error: libclang.a: 'ParseDecl.o': section header table goes past the end of > >>> the file: e_shoff = 0x131190 > > How big is the ParseDecl.o file that gets this report? > > </usr/obj/usr/src/arm.armv7/tmp/obj-tools/lib/clang/libclang/Parse/ParseDecl.o> # ls -l /usr/obj/usr/src/arm.armv7/tmp/obj-tools/lib/clang/libclang/Parse/ParseDecl.o -rw-r--r-- 1 root wheel 393216 May 3 19:15 /usr/obj/usr/src/arm.armv7/tmp/obj-tools/lib/clang/libclang/Parse/ParseDecl.o > > (Note the tmp/ in that path. Also the <> usage is in hopes of forming > one long line and are not part of the file path.) > Including the < and > in the pathname triggered a syntax error. Likely I misundersood the tip or I'm using a different shell. > > Can you publish the content of the file: > > </usr/obj/usr/src/arm.armv7/tmp/obj-tools/lib/clang/libclang/Parse_ParseDecl.o.meta> The file has been placed at http://www.zefox.net/~fbsd/rpi2/20260506/ After placing it there using sftp, running file on it locally reported fbsd@www:~/public_html/rpi2/20260506 % file * ParseDecl.o: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (FreeBSD), missing section headers at 1249720 Perhaps unsurpisingly it can't be viewed in a browser. It does display neatly (but unintelligibly to me) using hexdump. Thanks for writing, please indicate any more experiments that come to mind. bob prohaskahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aftVNo1vagUO9Xjs>