Date: Sat, 17 Jun 2023 16:05:12 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Armv7 linker failure on -current Message-ID: <F3F3300B-0817-4C23-8D16-B0E316C195D1@yahoo.com> In-Reply-To: <ZI3%2BooYV4xsyg5cZ@www.zefox.net> References: <ZI3EXC3kjZOyEdM6@www.zefox.net> <8B771495-1C68-4A23-8658-02A8AD28088B@yahoo.com> <ZI3%2BooYV4xsyg5cZ@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 17, 2023, at 11:42, bob prohaska <fbsd@www.zefox.net> wrote: > On Sat, Jun 17, 2023 at 08:34:16AM -0700, Mark Millard wrote: >> On Jun 17, 2023, at 07:34, bob prohaska <fbsd@www.zefox.net> wrote: >>=20 >>> A Pi2 running -current stops in buildworld with >>=20 >> I assume self building an update to main [so: 14]. >>=20 >=20 > Correct. >=20 >> What commit last built successfully? (This bounds what would be = different >> in official materials.) >>=20 >=20 > I haven't kept any manual records, but uname -a reports > FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #39 = main-9f135336f5: Fri Jun 16 02:18:02 PDT 2023 = bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm >=20 > Since my original post git pull found a few updates and I restarted = buildworld I expect that this means there is no evidence left to look at what was originally reported. > It has failed also, but with what looks like an unrelated error. These = problems > emerged after a silent hang using -j3, followed by power-cycling and = reboot. -j3 > was backed down to -j2 and buildworld restarted, with the mischief = reported here > ensuing. I see. Messy. > I'm starting to wonder if there's some undetected corruption in either = /usr/src > or /usr/obj. Perhaps I'd best run make cleandir twice and start over. = That will > likely take at least few days. This is a mechanical hard disk setup, = with 1 GB > swap. Boot is via microSD using only bootcode.bin, with the usual = msdos partition > on the hard disk. =20 >=20 > Is there a more expedient approach under the circumstances?=20 If I understand right, there is no evidence to examine from the original report's context to guide any investigation. It seems you need to establish a known context (broken or working) to possibly investigate. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F3F3300B-0817-4C23-8D16-B0E316C195D1>