mirror of
https://github.com/wolfSSL/wolfssl.git
synced 2026-07-05 20:40:50 +02:00
Juliusz Sosinowicz
85d3bc2380
wolfSSL's configure enables make's jobserver by default (AX_AM_JOBSERVER([yes]) -> AM_MAKEFLAGS += -j<nproc+1> in aminclude.am), and automake passes that explicit -j to every recursive sub-make, where it overrides the invoking make's job limit. The script's -j therefore only ever scheduled the outermost recursion hop: --jobs was inert. Measured on a 4-CPU host with 10 build-only configs oversaturating the worker pool, the jobserver default is also the better policy: capping sub-makes via --disable-jobserver and -j2 dropped CPU utilization from 96% to 89% and lengthened the wall time, because configs' serial phases (configure, link) stopped being backfilled by other configs' compile jobs. So make is now invoked with no -j at all - parallelism within a config comes from the configure-default jobserver - and the misleading knob is gone, including the macOS job's --jobs 3.