From nobody Wed May 6 00:32:35 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4g9GY65fPbz6cxDn for ; Wed, 06 May 2026 00:32:10 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4g9GXz6tqQz3Y0n for ; Wed, 06 May 2026 00:32:03 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 6460WaQF055891 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 5 May 2026 17:32:36 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 6460Wa35055890; Tue, 5 May 2026 17:32:36 -0700 (PDT) (envelope-from fbsd) Date: Tue, 5 May 2026 17:32:35 -0700 From: bob prohaska To: bob prohaska Cc: freebsd-current@freebsd.org Subject: Re: ar: error: libclang.a: 'ParseDecl.o': section header table goes past EOF Message-ID: References: <2c2ab68d-83eb-4b6d-996d-10c2169a2165@yahoo.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2c2ab68d-83eb-4b6d-996d-10c2169a2165@yahoo.com> X-Spamd-Result: default: False [0.70 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.66)[-0.661]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; NEURAL_SPAM_MEDIUM(0.46)[0.460]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[zefox.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4g9GXz6tqQz3Y0n 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 > > That error message can happen for the file content being corrupted. One > form of corruption can be truncated because of running out of file > system space. But there can be many others. Failed writes or later > read-back problems are possibilities. Bad RAM content that was written > out could be involved. > > Did you check the console output/log for any messages that might have > been from the time frame(s) for the file generation or read-back? > > > *** [libclang.a] Error code 1 > > .... > > make[4]: stopped making "all" in /usr/src/lib/clang/libclang > > .ERROR_TARGET='libclang.a' > > .ERROR_META_FILE='/usr/obj/usr/src/arm.armv7/tmp/obj-tools/lib/clang/libclang/li > > bclang.a.meta' > > .MAKE.LEVEL='4' > > ............ > > > > /usr/src was updated 5/4/26. > > > > Re-running git pull reports: > > Updating 8e8d87856241..9f2ad7c09709 > > and it looks as if only sbin and sys > > files have changed. > > > > I'll run a make cleandir and try again. If there are > > other things to try please let me know. > > There are a rather wide range of possibilities. If it turns out to not > be readily reproducible, then the details may never be known. It seems to be quite reproducible. After two runs of make cleandir and a git pull (which did find updates) the error repeats. Thanks for reading, suggestions welcome! bob prohaska