Re: ar: error: libclang.a: 'ParseDecl.o': section header table goes past EOF [So far: unable to reproduce, even based on llvm19 involvement]

Hi Mark,

On Sat, May 09, 2026 at 08:56:32PM -0700, Mark Millard wrote:
> On 5/9/26 18:41, bob prohaska wrote:
> > . . .
> > 
> > It looks as if running make kernel-toolchain somehow worked around
> > the failure. It completed successfully and is now running a normal
> > buildworld, which is in the building libraries stage. 
> 
> Good.
> 
> What was the context like just before you ran kernel-toolchain? Had you
> cleaned everything out to start over? Or was the old bad file and
> related materials still in place? Was this jsut after doing another
> source update?
> 
> When you did the kernel-toolchain was it -j1 (or no -j at all) style?
> Some other -jN ? How did that compare to prior build attempts that failed?
> 
> Does the Parse/ParseDecl.o file look appropriately sized now? (My guess
> is: yes.)
> 
> > 
> > Hopefully it'll finish within a day or two.
> > 
> > Thanks for writing, apologies if I jumped the gun!
> 
> You have no reason to be waiting for me.

Perhaps not, but you put some thought into a reply
that couldn't be acted on. I'm grateful for those
thoughts! 

After make buildworld completed successfully a 
subsequent git pull found a significant number of
updates, so make buildworld is running again to 
catch up.

One lingering puzzle is whether it's prudent to
run make installworld following a git pull that
finds updates which appear inconsequential, for
example man pages, tests or unused features like
zfs or tests. Doing so saves quite some time on 
a Pi2. Does it introduce hazardous inconsistencies?

Thanks for writing!

bob prohaska