Date: Thu, 7 May 2026 17:50:30 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-current@freebsd.org, dim@freebsd.org Subject: Re: ar: error: libclang.a: 'ParseDecl.o': section header table goes past EOF [So far: unable to reproduce, even based on llvm19 involvement] Message-ID: <6ae013cb-2e90-4e08-bac4-001fc8bc051c@yahoo.com> In-Reply-To: <af0kc8imCEmhJg7t@www.zefox.net> References: <2c2ab68d-83eb-4b6d-996d-10c2169a2165@yahoo.com> <afqMIyNQGtJpRQGS@www.zefox.net> <4fab914f-ff17-4312-a098-975b6c103e05@yahoo.com> <aftVNo1vagUO9Xjs@www.zefox.net> <413d71d1-6e18-4c7f-8844-d85c304d0504@yahoo.com> <aftnPgIVu6KNaAro@www.zefox.net> <33436574-0b2b-4db8-a69f-85df46af12a6@yahoo.com> <7e29fc11-9fcc-4a71-97bb-b709862e35e1@yahoo.com> <ad673dfe-caeb-41eb-8be1-77d1028dba71@yahoo.com> <9ff7855f-2b48-4cac-a82d-2cbd9912dc27@yahoo.com> <af0kc8imCEmhJg7t@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On 5/7/26 16:46, bob prohaska wrote: > On Thu, May 07, 2026 at 02:33:13PM -0700, Mark Millard wrote: >> >> How old is your environment that is using llvm19? What commit is it >> based on? > > Not sure I understand all of what you're asking. You supplied the kind of information I was looking for. The system reports > # uname -apKU > FreeBSD pelorus.zefox.org 16.0-CURRENT FreeBSD 16.0-CURRENT #37 main-n285410-c0c7d1e1af4e: Thu Apr 30 07:36:49 PDT 2026 bob@pelorus.zefox.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm armv7 1600016 1600016 Sat, 25 Apr 2026 (UTC) git: c0c7d1e1af4e - main - split.1: grammar Maxim Konovalov Your Apr 30 PDT date is likely from the time it took to build once you started that. That is about 6 main commits before the changes for llvm21 started later that same day (Apr-25 UTC). There are no armv7 *.txz artifacts after 2026-Apr-23 18:20 until 2026-Apr-27 18:43. So I can not match c0c7d1e1af4e via using an artifact build. What I tested was the armv7 026-Apr-23 18:20 artifact build, as close (in time) of a pre-llvm21-changes armv7 artifact as is available. I do not know why the artifact builders stopped building artifacts for a time. You landed in the middle of that range. I wonder if you are seeing part of why the builders were not producing builds. But I've no evidence of that. > > Apart from setting up meta mode no intentional changes have been made. Buildworld runs > as root with no jails or other sophistications. The filesystem is UFS running a usb- > attached SATA hard disk. > > One think I'm not sure of is the present revision of the source tree. Warning: line wrapping happens below that needs to be fixed. # cat ~/fbsd-based-on-what-commit.sh #! /bin/sh git $* log --oneline --no-color -n 1 \ && env TZ=UTC git $* log --format=fuller --date=iso-local -n 1 | grep -E "^(Commit|Author:)" \ && branch="`git $* branch --show-current`" \ && echo "branch: $branch" \ && base="`git $* merge-base freebsd/$branch HEAD`" \ && git $* log --oneline --no-color $base..HEAD \ && base_date="`env TZ=UTC git $* log --format=fuller --date=iso-local --no-color $base^..$base | grep CommitDate:`" \ && echo "merge-base: $base" \ && echo "merge-base: $base_date" \ && echo "n`git $* rev-list --first-parent --count $base` (--first-parent --count for merge-base)" With that set executable, a command like: ~/fbsd-based-on-what-commit.sh -C /usr/src should help if it is a git maintained source tree. In my context for the /usr/src-alt/ that I used: # ~/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 <kib@FreeBSD.org> Commit: Konstantin Belousov <kib@FreeBSD.org> 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 > Git status > doesn't report that info in terms of commit number or hash. Src was last updated > earlier today. > > If I missed the point please indicate so. You supplied what I was after. Thanks. I'm still no closer to having an idea what else to do for investigation. So far, you have the only known example failure context. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ae013cb-2e90-4e08-bac4-001fc8bc051c>