Date: Wed, 2 Oct 2024 04:28:09 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: FYI: make's "max_jobs" needs to be separated from -j (now?) Message-ID: <Zv0uSUVsyhRtMS27@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--xv61tAjw5LVxBNIo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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 t=
hat CC=3Dcc matches the source tree. Not bootstrapping a cross-compiler.
| make[1]: "/usr/src/Makefile.inc1" line 367: SYSTEM_LINKER: Determined tha=
t LD=3Dld 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
|=20
| make[1]: stopped making "buildworld" in /usr/src
| .ERROR_TARGET=3D'_cleanworldtmp'
| .ERROR_META_FILE=3D''
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).... :-}
(Now, if I could figure out why xdm built (and which runs fine) under
stable/14 now just mutters "exit status 1" when invoked under head, that
would be Quite Nice. I don't *think* it involves attempts to use "errno"
as a symbol -- at least, nm didn't see such a reference in the
unstripped executable I had lying about.)
Anyway: just in case there's someone else out there encountering the
above, this may shed a bit of light.
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Appeasement in 1938 did not bring peace in 1939.
What would appeasement bring now?
See https://www.catwhisker.org/~david/publickey.gpg for my public key.
--xv61tAjw5LVxBNIo
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iNUEARYKAH0WIQSTLzOSbomIK53fjFliipiWhXYx5QUCZv0uSV8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTMy
RjMzOTI2RTg5ODgyQjlEREY4QzU5NjI4QTk4OTY4NTc2MzFFNQAKCRBiipiWhXYx
5dvmAQDU+1cfIFH9SSPz2jPfUW6Kc48s9Qb2tMdbUf2UJjr6vAD/fvln1/A/ioJo
cdLTvlLS35cHPrJGDMiaXK1e+KtIkgw=
=6jAH
-----END PGP SIGNATURE-----
--xv61tAjw5LVxBNIo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zv0uSUVsyhRtMS27>