RE: make_jobs

void <void_at_f-m.fm> wrote on
Date: Sun, 09 Nov 2025 01:50:23 UTC : 

> Can make_jobs=N go in /etc/src.conf for making things like buildkernel?
> I'm asking because it's not in the manpage for src.conf.
> I understand its functionality for ports in /etc/make.conf
> Ideally I'd have make_jobs=N in src.conf and make_jobs=N+3
> in /etc/make.conf

poudriere(-devel) has a bunch of alternate make.conf
places that are local to that activity.

Do you use a poudriere(-devel)? Do you build ports or
port-packages some other way?

The below are from/for /usr/ports/Mk/bsd.port.mk .
They are not part of the FreeBSD-system build
environment.

MAKE_JOBS_UNSAFE
DISABLE_MAKE_JOBS
MAKE_JOBS_NUMBER
MAKE_JOBS_NUMBER_LIMIT

(I'm not aware of any "make_jobs" style of notation.)

> A side note:
> A similar sort of thing, PORTS_MODULES+=sysutils/lsof works in
> *either* src.conf or make.conf.... Confusingly.

QUOTE from man make.conf
     The file make.conf contains system-wide settings that will apply to every
     build using make(1) and the standard sys.mk file.  This is achieved as
     follows: make(1) processes the system makefile sys.mk before any other
     file by default, and sys.mk includes make.conf.
END QUOTE

So /etc/make.conf (normally) is not specific to building ports
or port-packages: it is also used for system builds. If you
list things documented to be for /etc/src.conf in /etc/make.conf
then system builds will use them but port/port-package builds
would happen to ignore them (despite the definitions being in
place).

The paths are defaults that can be overridden via defining
make variables:

__MAKE_CONF
SRCCONF
SRC_ENV_CONF

Thus you can have control over what file you want to use each
time.


===
Mark Millard
marklmi at yahoo.com