Re: FYI: make's "max_jobs" needs to be separated from -j (now?)
- Reply: Dan Mack : "Re: FYI: make's "max_jobs" needs to be separated from -j (now?)"
- Reply: David Wolfskill : "Re: FYI: make's "max_jobs" needs to be separated from -j (now?)"
- Reply: Graham Perrin : "1500024, libmd.so.6 and libmd.so.7 (was: FYI: make's "max_jobs" needs to be separated from -j (now?))"
- In reply to: David Wolfskill : "FYI: make's "max_jobs" needs to be separated from -j (now?)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 02 Oct 2024 13:19:25 UTC
David Wolfskill wrote: > I have been tracking stable/ and head (daily, with a few exceptions) for > many years, now. Over time, I set up a set of ([t]csh) aliases to > simplify the exercise for me. > > Until yesterday, the "make -j${max_jobs} buildworld" construct had > worked without issue, but (yesterday), the invocation failed quite > quickly: > > | Tue Oct 1 11:54:18 UTC 2024 > | --- buildworld --- > | make[1]: "/usr/src/Makefile.inc1" line 362: SYSTEM_COMPILER: Determined that CC=cc matches the source tree. Not bootstrapping a cross-compiler. > | make[1]: "/usr/src/Makefile.inc1" line 367: SYSTEM_LINKER: Determined that LD=ld matches the source tree. Not bootstrapping a cross-linker. > | -------------------------------------------------------------- > | >>> World build started on Tue Oct 1 11:54:18 UTC 2024 > | -------------------------------------------------------------- > | >>> Deleting stale files in build tree... > | 0.14 real 0.23 user 0.10 sys > | *** [_cleanworldtmp] Error code 6 > | > | make[1]: stopped making "buildworld" in /usr/src > | .ERROR_TARGET='_cleanworldtmp' > | .ERROR_META_FILE='' > > On a bit of a whim, I tried adjusting the "max_jobs" values (downward), > which didn't help, but removing the "-j14" entirely did not produce a > failure. > > On the other hand, rebuilding clang/llvm with a single core on a laptop > (when I actually want to be able to use the laptop later in the day > while I'm at work) didn't seem productive. > > A bit more rather randomly "trying stuff" yielded the result that while > > make -j14 buildworld > > failed (as described above), > > make -j 14 buildworld > > carries on as before -- it's building lib/clang (and using multiple > cores to do so).... :-} Just got the same error, but both invocations didn't work, and I noticed that bootstrapped version of mtree failed to run because of (now) missing libmd.so.6. I think it's not really related to whitespace between -j and jobs number, rather you had to (re)build the bootstrap tools.