Date: Thu, 11 Nov 2021 14:26:15 -0700 From: Warner Losh <imp@bsdimp.com> To: Jeffrey Bouquet <jbtakk@iherebuywisely.com> Cc: current <current@freebsd.org> Subject: Re: buildworld question. Message-ID: <CANCZdfrvRGO_rvd9E9=Eax2%2B4hsnoZU7_WKhwjq_ctTyz8QJig@mail.gmail.com> In-Reply-To: <E1mlHYI-0002Y6-1B@rmmprod07.runbox> References: <CANCZdfoUw3hKs2bTREGPGq_cBEJR_zPQmNM_On3To3N2T4S1oQ@mail.gmail.com> <E1mlHYI-0002Y6-1B@rmmprod07.runbox>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000c6772805d089fe15 Content-Type: text/plain; charset="UTF-8" On Thu, Nov 11, 2021, 2:24 PM Jeffrey Bouquet <jbtakk@iherebuywisely.com> wrote: > > > On Thu, 11 Nov 2021 08:53:47 -0700, Warner Losh <imp@bsdimp.com> wrote: > > > On Thu, Nov 11, 2021 at 5:48 AM Jeffrey Bouquet < > jbtakk@iherebuywisely.com> > > wrote: > > > > > Apologies if this applies to STABLE 13, but git is involved... > > > buildworld is failing 4 minutes or so in. > > > would it be useful to re-git the /usr/src? > > > Is there a way to run "make buildworld" for a LESS terse error result? > > > Any other 3rd method to debug the error? > > > > > > > .......................................................................................... > > > /usr/local/bin/clang12 ..... -o machdep_ldisx.o > > > In file included from /usr/src/lib/libc/gdtoa/machdep_ldisx.c:45: > > > In file included from /usr/src/contrib/gdtoa/gdtoaimp.h:202: > > > In file included from /usr/src/include/pthread.h:49: > > > /usr/src/include/time.h: fatal error: 'sys/_clock_id.h' file not found > > > #include <sys/_clock_id.h> > > > > ......................................................................... > > > I also suspect the missing file might be a malformed missing > > > symlink instead... because the file exists at least once. > > > The error does not indicate from what [ 2nd ] subdir it, or a symlink, > is > > > missing ?? > > > > > > src.conf has several lines such as WITHOUT_CPP=yes, meant I think > > > to reduce build times if that matters. > > > > > > It likely does. It likely means that that file wasn't properly staged and > > so the build is failing. > > > > I'd bisect the file of omissions to see if that's the cause. I'd start by > > removing them all > > and seeing if the problem persists. Not all combinations are supported, > nor > > are > > the vast majority of all bad combinations detected with a nice error > > message. > > > > Warner > > > Same error with the file removed. Next step remove /usr/src and re-git I Try 'git reset --hard'. That will give you a clean tree. Also, what does git status say? > --000000000000c6772805d089fe15--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrvRGO_rvd9E9=Eax2%2B4hsnoZU7_WKhwjq_ctTyz8QJig>