Re: "make installworld" fails ("Signal 11")
Warner Losh <[email protected]>
| Newsgroups | gmane.os.freebsd.current |
|---|---|
| Message-ID | <CANCZdfr=ZTBOzaEer4sH69wSCRROXfmrEJJAoC6TTmKVtwYMjg@mail.gmail.com> |
On Wed, Aug 5, 2026 at 6:55 AM David Wolfskill <[email protected]> wrote: > On Wed, Aug 05, 2026 at 01:47:47PM +0200, Kristof Provost wrote: > > On 5 Aug 2026, at 13:32, David Wolfskill wrote: > > > System was running: > > > FreeBSD freebeast.catwhisker.org 16.0-CURRENT FreeBSD 16.0-CURRENT > #654 main-n287946-ddd850aa7720: Tue Aug 4 12:29:15 UTC 2026 > [email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 1600019 1600019 > > ... > > I believe I ran into the same thing yesterday, but it went away after I > deleted /usr/obj/* and built again. > > It may be worth trying the same. > > .... > > Hmm... OK; I first tried merely re-starting the 'make installworld." > That merely reproduced the observed failure. > > Then I "rm -fr /usr/obj/usr/src/amd64.amd64", then started the build > over. > > That has worked: > > FreeBSD 16.0-CURRENT #0 main-n287957-4ebcdb8dd9a7: Wed Aug 5 12:40:15 UTC > 2026 [email protected]:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 1600019 1600019 > We likely need an UPDATING entry for this. Times when a clean build is needed should be rare and either we fix the underlying problem, or we document the problem. I've seen no motion towards the former, so the latter seems appropriate. Warner