A quick note about devel/afl++

Hi,

One of my NetBSD 11 PowerPC build machines is a single core PowerPC Mac 
mini with 1 gig of memory. For obvious reasons, I run this system without 
MAKE_JOBS.

I happened to be logged in when I saw this while the system was compiling 
devel/afl++ from 2026Q2:

load averages:  12.2,  10.1,  6.12;               up 13+01:09:08             03:01:24
52 processes: 1 runnable, 50 sleeping, 1 on CPU
CPU states:  0.2% user, 31.2% nice, 22.9% system,  0.2% interrupt, 45.4% idle
Memory: 547M Act, 267M Inact, 88K Wired, 82M Exec, 79M File, 2184K Free
Swap: 2048M Total, 674M Used, 1374M Free / Pools: 159M Used / Network: 8K In, 16K Out

   PID USERNAME PRI NICE   SIZE   RES STATE       TIME   WCPU    CPU COMMAND
     0 root     222    0     0K   76M ifwdog    417:50 36.87% 36.87% [system]
16737 pbulk     22    4   313M  159M RUN         0:48 15.28% 15.28% clang++
23548 pbulk     76    4   298M  140M biowait     0:43 12.70% 12.70% clang++
27709 pbulk     81    4   260M  106M biowait     0:32  3.32%  3.32% clang++
13618 pbulk     82    4   255M   98M biowait     0:31  2.34%  2.34% clang++
24540 pbulk     83    4   256M   76M biowait     0:30  2.10%  2.10% clang++
14430 pbulk     82    4   247M   79M biowait     0:28  1.71%  1.71% clang++
  7083 pbulk     83    4   253M   63M biowait     0:29  1.66%  1.66% clang++
28896 pbulk     83    4   247M   79M biowait     0:28  1.46%  1.46% clang++
26547 pbulk     83    4   236M   60M biowait     0:25  1.37%  1.37% clang++
29165 pbulk     83    4   244M   71M biowait     0:27  1.32%  1.32% clang++
22673 pbulk     83    4   256M   74M biowait     0:30  1.27%  1.27% clang++

I remember there were issues with rust ignoring MAKE_JOBS in the past, but 
that was on systems with multiple cores where rust used all the cores no 
matter what. But where would afl++ get the idea that more than one job 
simultaneously make sense?

John