From nobody Thu May 07 19:24:41 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 4gBMdb6kFPz6d3Vm for ; Thu, 07 May 2026 19:24:51 +0000 (UTC) (envelope-from freebsd-current@m.gmane-mx.org) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gBMdY4l6bz47cN for ; Thu, 07 May 2026 19:24:49 +0000 (UTC) (envelope-from freebsd-current@m.gmane-mx.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=yahoo.com (policy=reject); spf=pass (mx1.freebsd.org: domain of freebsd-current@m.gmane-mx.org designates 116.202.254.214 as permitted sender) smtp.mailfrom=freebsd-current@m.gmane-mx.org Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1wL4L1-0007Aw-NX for freebsd-current@freebsd.org; Thu, 07 May 2026 21:24:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Millard Subject: Re: ar: error: libclang.a: 'ParseDecl.o': section header table goes past EOF [Looks to be: armv7 llvm19 fails to build bootstrap llvm21] Date: Thu, 7 May 2026 12:24:41 -0700 Message-ID: References: <2c2ab68d-83eb-4b6d-996d-10c2169a2165@yahoo.com> <4fab914f-ff17-4312-a098-975b6c103e05@yahoo.com> <413d71d1-6e18-4c7f-8844-d85c304d0504@yahoo.com> <33436574-0b2b-4db8-a69f-85df46af12a6@yahoo.com> <7e29fc11-9fcc-4a71-97bb-b709862e35e1@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=UTF-8 Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird Cc: freebsd-current@freebsd.org, dim@FreeBSD.org Content-Language: en-US In-Reply-To: <7e29fc11-9fcc-4a71-97bb-b709862e35e1@yahoo.com> X-Spamd-Result: default: False [3.69 / 15.00]; DMARC_POLICY_REJECT(2.00)[yahoo.com : SPF not aligned (relaxed), No valid DKIM,reject]; NEURAL_SPAM_MEDIUM(0.99)[0.990]; NEURAL_SPAM_SHORT(0.83)[0.832]; NEURAL_HAM_LONG(-0.83)[-0.829]; MV_CASE(0.50)[]; FORGED_SENDER(0.30)[marklmi@yahoo.com,freebsd-current@m.gmane-mx.org]; R_SPF_ALLOW(-0.20)[+mx]; ONCE_RECEIVED(0.20)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:24940, ipnet:116.202.0.0/16, country:DE]; R_DKIM_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; FROM_NEQ_ENVFROM(0.00)[marklmi@yahoo.com,freebsd-current@m.gmane-mx.org] X-Spamd-Bar: +++ X-Rspamd-Queue-Id: 4gBMdY4l6bz47cN On 5/7/26 09:05, Mark Millard wrote: > On 5/6/26 19:59, Mark Millard wrote: >> On 5/6/26 09:07, bob prohaska wrote: >>> On Wed, May 06, 2026 at 08:54:32AM -0700, Mark Millard wrote: >>>> On 5/6/26 07:50, bob prohaska wrote: >>>>> 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: >> >> Which is true of the context: >> >> ) Is the old system one still using the llvm19 based clang related >> toolchain --so that the build needs to bootstrap the llvm21 based >> one? >> vs. >> ) Is the old system one already using the new llvm21 based clang-related >> toolchain --so that no bootstrap toolchain is needed (even if one is >> being built)? >> >>>>>>>>> >>>>>>>>> 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? >>>>>> >>>>>> >>>>> >>>>> # 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 >>>> >>>> That earlier 0x131190 was a offset in the file. 0x131190 == 1249680 . >>>> That is a lot bigger than 393216. >>>> >>>>> >>>>>> >>>>>> (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. >>>> >>>> Only use the text inside the <>'s. >>>> >>>> The <>'s are an attempt to prevent the message I send from splitting the >>>> long text into more than one line in the process --even if I do not >>>> split it myself. Otherwise you might have to splice together the full >>>> path. Adding spaces just inside the <>'s would not work for the purpose, >>>> thus the lack of such spaces. >>> Ahhh, so user escapes, not shell escapes 8-) >>> >>>>> >>>>> >>>>>> >>>>>> Can you publish the content of the file: >>>>>> >>>>>> >>>>> >>>>> The file has been placed at >>>>> http://www.zefox.net/~fbsd/rpi2/20260506/ >>>> >>>> You published ParseDecl.o instead of publishing Parse_ParseDecl.o.meta . >>>> >>>> Parse_ParseDecl.o.meta is a text file produced by use of META_MODE . I >>>> expect it will include the text of the command that produced >>>> ParseDecl.o . >>>> >>>> Like earlier: omit the <> characters when extracting the path. >>>> >>> Apologies for the blunder! The correct file is now at: >>> http://www.zefox.net/~fbsd/rpi2/20260506/Parse_ParseDecl.o.meta >>> >>> Thanks for writing, and your patience! >>> >>> bob prohaska >>> >>> >> >> My guess is that, for an initially empty build tree in a armv7 context, >> a command sequence like: >> >> # cd /usr/src/ >> # env WITH_META_MODE= \ >> make -j3 \ >> WITHOUT_SYSTEM_COMPILER= \ >> WITHOUT_SYSTEM_LINKER= \ >> kernel-toolchain >> >> may be sufficient to have: >> >> >> >> generated instead of skipped, via avoiding use of the system >> compiler/linker, even if they are llvm21 based already. (In my >> context they are llvm21 based, as it is a preexisting upstream pkgbase >> distribution install from after llvm21 was updated that is doing the build.) >> >> I have such a llvm21-context build going in an armv7 chroot (in a >> context were -j8 is reasonable). Still, it is going to be some time >> before I know if the build repeated the problem vs. not. >> >> It may be that one has to start with an llvm19-based context to see the >> problem. I do not have such a llvm19 context available. >> >> > > Bob sent Email that was not sent to the list that reported his context > upgrade context is starting with an environment that has: > > QUOTE > Clang -v reports > FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git > llvmorg-19.1.7-0-gcd708029e0b2) > Target: armv7-unknown-freebsd16.0-gnueabihf > Thread model: posix > InstalledDir: /usr/bin > Build config: +assertions > END QUOTE > > My test case was llvm21 based, no bootsrap needed --but when Iforced a > boostrap, llvm21 boostrapped itself just fine. > > Thus, it looks like the armv7 llvm19 context has a problem that prevents > source code building the llvm21 bootstrap context correctly. > > > At this time I do not have an armv7 llvm19 based context to > independently test. > > [dim@ may be interested in this point:] I will note that the in-progress 15.1-RELEASE is based on the llvm19 related toolchain. So, later when, say, 15.2-RELEASE tries to be based on llvm21 (or later) instead, this problem for armv7 may well repeat in the official release sequence. As for main, I now have a chroot based on: which is old enough to be llvm19 based. It is attempting a kernel-toolchain build based on building: # ~/fbsd-based-on-what-commit.sh -C /usr/src-alt/ 839d3266d8c6 (HEAD -> main, freebsd/main, freebsd/HEAD) uipc_shm.c: make large page allocation interruptible Author: Konstantin Belousov Commit: Konstantin Belousov CommitDate: 2026-05-01 01:06:42 +0000 branch: main merge-base: 839d3266d8c6f6471cb92a3c0ae32eb16d117427 merge-base: CommitDate: 2026-05-01 01:06:42 +0000 n285621 (--first-parent --count for merge-base) We will see what it does for: tmp/obj-tools/lib/clang/libclang/Parse/ParseDecl.o -- === Mark Millard marklmi at yahoo.com