SRC.CONF(5)

๐Ÿ“ฆ
version 15.1 ยท 3 versions
, in freebsd 15.1

๐ŸŽ€ SRC.CONF(5) ๐ŸŽ€

okay bestie, this is the File Formats Manual page for src.conf โ€” source build options. itโ€™s giving very โ€œlet me control the whole buildโ€ energy, and honestly? iconic. ๐Ÿ’…โœจ

๐ŸŒธ NAME ๐ŸŒธ

src.conf โ€” source build options ๐Ÿ› ๏ธ๐Ÿ’–

๐Ÿ’œ DESCRIPTION ๐Ÿ’œ

okay so src.conf is literally the file that contains variables controlling what components get generated during the build process of the FreeBSD source tree; see build(7). ๐Ÿฆ‹

src.conf uses the standard makefile syntax. however โ€” and this is important, bestie โ€” src.conf should not specify any dependencies to make(1). instead, src.conf is there to set make(1) variables that control the aspects of how the system builds. no cap. โœจ

the default location of src.conf is the top level of the source tree, or /etc/src.conf if no src.conf is found in the source tree itself, though an alternative location can be specified in the make(1) variable SRCCONF. overriding the location of src.conf may be necessary if the system-wide settings are not suitable for a particular build. for instance, setting SRCCONF to /dev/null effectively resets all build controls to their defaults. ๐Ÿซถ

the only purpose of src.conf is to control the compilation of the FreeBSD source code, which is usually located in /usr/src. as a rule, the system administrator creates src.conf when the values of certain control variables need to be changed from their defaults. ๐Ÿ’–

in addition, control variables can be specified for a particular build via the -D option of make(1) or in its environment; see environ(7). ๐ŸŒˆ

the environment of make(1) for the build can be controlled via the SRC_ENV_CONF variable, which defaults to /etc/src-env.conf. some examples that may only be set in this file are WITH_DIRDEPS_BUILD, and WITH_META_MODE, and MAKEOBJDIRPREFIX as they are environment-only variables. ๐Ÿงš

the values of WITH_ and WITHOUT_ variables are ignored regardless of their setting; even if they would be set to FALSE or NO. the presence of an option causes it to be honored by make(1). ๐Ÿ‘‘

this list provides a name and short description for variables that can be used for source builds. ๐ŸŽ€


  • WITHOUT_ACCT โ€” do not build process accounting tools such as accton(8) and sa(8).
  • WITHOUT_ACPI โ€” do not build acpiconf(8), acpidump(8) and related programs.
  • WITHOUT_APM โ€” do not build apm(8), apmd(8) and related programs.
  • WITH_ASAN โ€” build the base system with Address Sanitizer (ASan) to detect memory corruption bugs such as buffer overflows or use-after-free. requires that Clang be used as the base system compiler and that the runtime support library is available. when set, it enforces these options:
    • WITH_LLVM_BINUTILS
    • WITH_LLVM_CXXFILT
  • WITHOUT_ASSERT_DEBUG โ€” compile programs and libraries without the assert(3) checks.
  • WITHOUT_AT โ€” do not build at(1) and related utilities.
  • WITHOUT_AUDIT โ€” do not build audit support into system programs.
  • WITHOUT_AUTHPF โ€” do not build authpf(8).
  • WITHOUT_AUTOFS โ€” do not build autofs(4) related programs, libraries, and kernel modules.
  • WITHOUT_AUTO_OBJ โ€” disable automatic creation of objdirs. this is enabled by default if the wanted OBJDIR is writable by the current user.

this must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf. โš ๏ธ

  • WITH_BEARSSL โ€” build the BearSSL library.

BearSSL is a tiny SSL library suitable for embedded environments. for details see https://www.BearSSL.org/ โœจ

this library is currently only used to perform signature verification and related operations for Verified Exec and loader(8).

due to size constraints in the BIOS environment on x86, one may need to set LOADERSIZE larger than the default 500000, although often loader is under the 500k limit even with this option. setting LOADERSIZE larger than 500000 may cause pxeboot(8) to be too large to work. careful testing of the loader in the target environment when built with a larger limit to establish safe limits is critical because different BIOS environments reserve differing amounts of the low 640k space, making a precise limit for everybody impossible. ๐Ÿ˜ญ

see also WITH_LOADER_PXEBOOT for other considerations. when set, these options are also in effect:

  • WITH_LOADER_EFI_SECUREBOOT (unless WITHOUT_LOADER_EFI_SECUREBOOT is set explicitly)
  • WITH_LOADER_VERIEXEC (unless WITHOUT_LOADER_VERIEXEC is set explicitly)
  • WITH_LOADER_VERIEXEC_VECTX (unless WITHOUT_LOADER_VERIEXEC_VECTX is set explicitly)
  • WITH_VERIEXEC (unless WITHOUT_VERIEXEC is set explicitly)
  • WITHOUT_BHYVE โ€” do not build or install bhyve(8), associated utilities, and examples.

this option only affects amd64/amd64 and arm64/aarch64.

  • WITH_BHYVE_SNAPSHOT โ€” include support for save and restore (snapshots) in bhyve(8) and bhyvectl(8).

this option only affects amd64/amd64.

  • WITH_BIND_NOW โ€” build all binaries with the DF_BIND_NOW flag set to indicate that the run-time loader should perform all relocation processing at process startup rather than on demand. the combination of the BIND_NOW and RELRO options provide โ€œfullโ€ Relocation Read-Only (RELRO) support. with full RELRO the entire GOT is made read-only after performing relocation at startup, avoiding GOT overwrite attacks. ๐Ÿ”ฅ
  • WITHOUT_BLACKLIST โ€” this option has been renamed to WITHOUT_BLOCKLIST. when set, it enforces these options:
    • WITHOUT_BLOCKLIST

when set, these options are also in effect:

  • WITHOUT_BLACKLIST_SUPPORT (unless WITH_BLACKLIST_SUPPORT is set explicitly)
  • WITHOUT_BLOCKLIST_SUPPORT (unless WITH_BLOCKLIST_SUPPORT is set explicitly)
  • WITHOUT_BLACKLIST_SUPPORT โ€” this option has been renamed to WITHOUT_BLOCKLIST_SUPPORT. when set, it enforces these options:
    • WITHOUT_BLOCKLIST_SUPPORT
  • WITHOUT_BLOCKLIST โ€” set this if you do not want to build blocklistd(8) and blocklistctl(8). when set, it enforces these options:
    • WITHOUT_BLACKLIST

when set, these options are also in effect:

  • WITHOUT_BLACKLIST_SUPPORT (unless WITH_BLACKLIST_SUPPORT is set explicitly)
  • WITHOUT_BLOCKLIST_SUPPORT (unless WITH_BLOCKLIST_SUPPORT is set explicitly)
  • WITHOUT_BLOCKLIST_SUPPORT โ€” build some programs without libblocklist(3) support, like fingerd(8) and sshd(8). when set, it enforces these options:
    • WITHOUT_BLACKLIST_SUPPORT
  • WITHOUT_BLUETOOTH โ€” do not build Bluetooth related kernel modules, programs and libraries.
  • WITHOUT_BOOT โ€” do not build the boot blocks and loader.
  • WITHOUT_BOOTPARAMD โ€” do not build or install bootparamd(8).
  • WITHOUT_BOOTPD โ€” do not build or install bootpd(8).
  • WITH_BRANCH_PROTECTION โ€” build with branch protection enabled. on arm64 enable the use of pointer authentication and branch target identification instructions on arm64. these can be used to help mitigate some exploit techniques. ๐Ÿ›ก๏ธ
  • WITHOUT_BSDINSTALL โ€” do not build bsdinstall(8), sade(8), and related programs.
  • WITHOUT_BSD_CPIO โ€” do not build the BSD licensed version of cpio based on libarchive(3).
  • WITHOUT_BSNMP โ€” do not build or install bsnmpd(1) and related libraries and data files.
  • WITHOUT_BZIP2 โ€” do not build contributed bzip2 software as a part of the base system. the option has no effect yet. when set, these options are also in effect:
    • WITHOUT_BZIP2_SUPPORT (unless WITH_BZIP2_SUPPORT is set explicitly)
  • WITHOUT_BZIP2_SUPPORT โ€” build some programs without optional bzip2 support.
  • WITHOUT_CALENDAR โ€” do not build calendar(1).
  • WITHOUT_CAROOT โ€” do not add the trusted certificates from the Mozilla NSS bundle to base.
  • WITHOUT_CASPER โ€” this option has no effect.
  • WITH_CCACHE_BUILD โ€” use ccache(1) for the build. no configuration is required except to install the devel/ccache or devel/sccache package. when using with distcc(1), set CCACHE_PREFIX=/usr/local/bin/distcc. when using with sccache set CCACHE_NAME=sccache in src.conf(5). the default cache directory of $HOME/.ccache will be used, which can be overridden by setting CCACHE_DIR. the CCACHE_COMPILERCHECK option defaults to content when using the in-tree bootstrap compiler, and mtime when using an external compiler. the CCACHE_CPP2 option is used for Clang but not GCC.

sharing a cache between multiple work directories requires using a layout similar to /some/prefix/src /some/prefix/obj and an environment such as:

CCACHE_BASEDIR='${SRCTOP:H}' MAKEOBJDIRPREFIX='${SRCTOP:H}/obj'

see ccache(1) for more configuration options. ๐Ÿ’–

  • WITHOUT_CCD โ€” do not build geom_ccd(4) and related utilities.
  • WITHOUT_CDDL โ€” do not build code licensed under Sun's CDDL. when set, it enforces these options:
    • WITHOUT_CTF
    • WITHOUT_DTRACE
    • WITHOUT_LOADER_ZFS
    • WITHOUT_ZFS
    • WITHOUT_ZFS_TESTS
  • WITHOUT_CLANG โ€” do not build the Clang C/C++ compiler during the regular phase of the build. when set, it enforces these options:
    • WITHOUT_CLANG_EXTRAS
    • WITHOUT_CLANG_FORMAT
    • WITHOUT_CLANG_FULL
    • WITHOUT_LLVM_COV

when set, these options are also in effect:

  • WITHOUT_LLVM_TARGET_AARCH64 (unless WITH_LLVM_TARGET_AARCH64 is set explicitly)
  • WITHOUT_LLVM_TARGET_ALL (unless WITH_LLVM_TARGET_ALL is set explicitly)
  • WITHOUT_LLVM_TARGET_ARM (unless WITH_LLVM_TARGET_ARM is set explicitly)
  • WITHOUT_LLVM_TARGET_POWERPC (unless WITH_LLVM_TARGET_POWERPC is set explicitly)
  • WITHOUT_LLVM_TARGET_RISCV (unless WITH_LLVM_TARGET_RISCV is set explicitly)
  • WITHOUT_CLANG_BOOTSTRAP โ€” do not build the Clang C/C++ compiler during the bootstrap phase of the build. to be able to build the system, either gcc or clang bootstrap must be enabled unless an alternate compiler is provided via XCC.
  • WITH_CLANG_EXTRAS โ€” build additional clang and llvm tools, such as bugpoint and clang-format.
  • WITH_CLANG_FORMAT โ€” build clang-format.
  • WITHOUT_CLANG_FULL โ€” bestie, this one says don't build the ARCMigrate, Rewriter and StaticAnalyzer components of the Clang C/C++ compiler. That's it, that's the whole vibe ๐Ÿ’…
  • WITH_CLEAN โ€” clean before building world and/or kernel. Lowkey important detail: recording a new epoch in .clean_build_epoch in the root of the source tree will also force a clean world build ๐Ÿงน When set, these options are also in effect:
    • WITHOUT_DEPEND_CLEANUP (unless WITH_DEPEND_CLEANUP is set explicitly)
  • WITHOUT_CPP โ€” do not build cpp(1) โœจ
  • WITHOUT_CROSS_COMPILER โ€” do not build any cross compiler in the cross-tools stage of buildworld. Okay so real talk: when you're compiling a different version of FreeBSD than what's installed on the system, provide an alternate compiler with XCC to ensure success ๐Ÿ”ฅ When compiling with an identical version of FreeBSD to the host, this option may be safely used. It may also be safe when the host version of FreeBSD is close to the sources being built โ€” but all bets are off if there have been any changes to the toolchain between the versions ๐Ÿ˜ญ When set, it enforces these options:
    • WITHOUT_CLANG_BOOTSTRAP
    • WITHOUT_ELFTOOLCHAIN_BOOTSTRAP
    • WITHOUT_LLD_BOOTSTRAP
  • WITHOUT_CRYPT โ€” do not build any crypto code ๐Ÿ” When set, it enforces these options:
    • WITHOUT_DMAGENT
    • WITHOUT_KERBEROS
    • WITHOUT_LDNS
    • WITHOUT_LDNS_UTILS
    • WITHOUT_LOADER_ZFS
    • WITHOUT_MITKRB5
    • WITHOUT_OPENSSH
    • WITHOUT_OPENSSL
    • WITHOUT_OPENSSL_KTLS
    • WITHOUT_PKGBOOTSTRAP
    • WITHOUT_UNBOUND
    • WITHOUT_ZFS
    • WITHOUT_ZFS_TESTS

When set, these options are also in effect:

  • WITHOUT_KERBEROS_SUPPORT (unless WITH_KERBEROS_SUPPORT is set explicitly)
  • WITH_CTF โ€” compile with CTF (Compact C Type Format) data. CTF data encapsulates a reduced form of debugging information similar to DWARF and the venerable stabs, and it's required for DTrace ๐Ÿ‘‘
  • WITHOUT_CUSE โ€” do not build CUSE-related programs and libraries.
  • WITHOUT_CXGBETOOL โ€” do not build cxgbetool(8)

This is a default setting on arm/armv7 and riscv/riscv64.

This is a default setting on amd64/amd64, arm64/aarch64, i386/i386, powerpc/powerpc64 and powerpc/powerpc64le.

  • WITHOUT_DEBUG_FILES โ€” avoid building or installing standalone debug files for each executable binary and shared library ๐Ÿซถ
  • WITHOUT_DEPEND_CLEANUP โ€” do not attempt to detect if the object tree needs cleaning in part or in whole before building. It speeds up incremental builds, especially when experimenting with build options โ€” but heads up, it may cause the build to inexplicably fail or produce non-functioning binaries ๐Ÿ’€
  • WITH_DETECT_TZ_CHANGES โ€” make the time handling code detect changes to the timezone files ๐Ÿ•
  • WITH_DIALOG โ€” do build dialog(1), dialog(3), dpv(1), and dpv(3).
  • WITHOUT_DICT โ€” do not build the Webster dictionary files ๐Ÿ“–
  • WITH_DIRDEPS_BUILD โ€” this is an alternate build system. For details see https://www.crufty.net/sjg/docs/freebsd-meta-mode.htm. Build commands can be seen from the top-level with:
make show-valid-targets

The build is driven by dirdeps.mk using DIRDEPS stored in Makefile.depend files found in each directory.

The build can be started from anywhere, and behaves the same. The initial instance of make(1) recursively reads DIRDEPS from Makefile.depend, computing a graph of tree dependencies from the current origin. Setting NO_DIRDEPS skips checking dirdep dependencies and will only build in the current and child directories. NO_DIRDEPS_BELOW skips building any dirdeps and only build the current directory.

This also utilizes the WITH_META_MODE logic for incremental builds.

The build hides commands executed unless NO_SILENT is defined.

Note that there is currently no mass install feature for this. This build is designed for producing packages, that can then be installed on a target system.

The implementation in FreeBSD is incomplete ๐Ÿ˜ญ Completion would require leaf directories for building each kernel and package so that their dependencies can be tracked. When set, it enforces these options:

  • WITH_INSTALL_AS_USER

When set, these options are also in effect:

  • WITH_META_ERROR_TARGET (unless WITHOUT_META_ERROR_TARGET is set explicitly)
  • WITH_META_MODE (unless WITHOUT_META_MODE is set explicitly)
  • WITH_STAGING (unless WITHOUT_STAGING is set explicitly)
  • WITH_STAGING_MAN (unless WITHOUT_STAGING_MAN is set explicitly)
  • WITH_STAGING_PROG (unless WITHOUT_STAGING_PROG is set explicitly)
  • WITH_SYSROOT (unless WITHOUT_SYSROOT is set explicitly)
This must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf.
  • WITH_DIRDEPS_CACHE โ€” cache the result of dirdeps.mk, which can save significant time for subsequent builds. Depends on WITH_DIRDEPS_BUILD.
This must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf.
  • WITH_DISK_IMAGE_TOOLS_BOOTSTRAP โ€” build etdump(1), makefs(8) and mkimg(1) as bootstrap tools ๐Ÿ’ฟ
  • WITHOUT_DMAGENT โ€” do not build dma Mail Transport Agent ๐Ÿ“ฌ
  • WITHOUT_DOCCOMPRESS โ€” do not install compressed system documentation. Only the uncompressed version will be installed.
  • WITHOUT_DTRACE โ€” do not build DTrace framework kernel modules, libraries, and user commands. When set, it enforces these options:
    • WITHOUT_CTF
  • WITH_DTRACE_ASAN โ€” compile userspace DTrace code (libdtrace, dtrace(1), lockstat(1), plockstat(1)) with address and undefined behavior sanitizers ๐Ÿงช Requires that Clang be used as the base system compiler and that the runtime support library is available.
  • WITH_DTRACE_TESTS โ€” build and install the DTrace test suite in /usr/tests/cddl/usr.sbin/dtrace. Heads up bestie: this test suite is considered experimental on architectures other than amd64/amd64 and running it may cause system instability ๐Ÿ’€
  • WITHOUT_DYNAMICROOT โ€” set this if you do not want to link /bin and /sbin dynamically.
  • WITHOUT_EE โ€” do not build and install edit(1), ee(1), and related programs.
  • WITHOUT_EFI โ€” set not to build efivar(3) and efivar(8).

This is a default setting on i386/i386, powerpc/powerpc64 and powerpc/powerpc64le.

This is a default setting on amd64/amd64, arm/armv7, arm64/aarch64 and riscv/riscv64.

  • WITHOUT_ELFTOOLCHAIN_BOOTSTRAP โ€” do not build ELF Tool Chain tools (addr2line, nm, size, strings and strip) as part of the bootstrap process. An alternate bootstrap tool chain must be provided ๐Ÿซถ
  • WITHOUT_EXAMPLES โ€” avoid installing examples to /usr/share/examples/.
  • WITH_EXPERIMENTAL โ€” include experimental features in the build ๐Ÿงš
  • WITHOUT_FDT โ€” do not build Flattened Device Tree support as part of the base system. This includes the device tree compiler (dtc) and libfdt support library.

This is a default setting on amd64/amd64 and i386/i386.

  • WITH_FDT โ€” build Flattened Device Tree support as part of the base system ๐ŸŒณ This includes the device tree compiler (dtc) and libfdt support library.

This is a default setting on arm/armv7, arm64/aarch64, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.

  • WITHOUT_FILE โ€” do not build file(1) and related programs.
  • WITHOUT_FINGER โ€” do not build or install finger(1) and fingerd(8) ๐Ÿ‘†
  • WITHOUT_FLOPPY โ€” do not build or install programs for operating floppy disk driver ๐Ÿ’พ
  • WITHOUT_FORMAT_EXTENSIONS โ€” do not enable -fformat-extensions when compiling the kernel. Also disables all format checking.
  • WITHOUT_FORTH โ€” build bootloaders without Forth support.
  • WITHOUT_FREEBSD_UPDATE โ€” do not build freebsd-update(8).
  • WITHOUT_FTP โ€” do not build or install ftp(1).
  • WITHOUT_GAMES โ€” do not build games ๐ŸŽฎ (tragic, I know)
  • WITHOUT_GNU_DIFF โ€” do not build GNU diff3(1); build BSD diff3(1) instead.
  • WITHOUT_GOOGLETEST โ€” neither build nor install library โ€œlibgmockโ€, library โ€œlibgtestโ€, and dependent tests.
  • WITHOUT_GPIO โ€” do not build gpioctl(8) as part of the base system.
  • WITHOUT_HAST โ€” do not build hastd(8) and related utilities.
  • WITH_HESIOD โ€” build Hesiod support.
  • WITHOUT_HTML โ€” do not build HTML docs.
  • WITHOUT_HYPERV โ€” do not build or install HyperV utilities.

This is a default setting on arm/armv7, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.

  • WITH_HYPERV โ€” build or install HyperV utilities โœจ

This is a default setting on amd64/amd64, arm64/aarch64 and i386/i386.

  • WITHOUT_ICONV โ€” do not build iconv as part of libc.
  • WITHOUT_INCLUDES โ€” do not install header files. Fun lore drop: this option used to be spelled NO_INCS ๐Ÿฆ‹ The option does not work for build targets.
  • WITHOUT_INET โ€” do not build programs and libraries related to IPv4 networking. When set, it enforces these options:
    • WITHOUT_INET_SUPPORT
  • WITHOUT_INET6 โ€” do not build programs and libraries related to IPv6 networking. When set, it enforces these options:
    • WITHOUT_INET6_SUPPORT
  • WITHOUT_INET6_SUPPORT โ€” build libraries, programs, and kernel modules without IPv6 support.
  • WITHOUT_INETD โ€” do not build inetd(8).
  • WITHOUT_INET_SUPPORT โ€” build libraries, programs, and kernel modules without IPv4 support.
  • WITHOUT_INSTALLLIB โ€” set this to not install optional libraries. For example, when creating a nanobsd(8) image. Heads up: the option does not work for build targets.
  • WITH_INSTALL_AS_USER โ€” makes install targets actually succeed for non-root girlies ๐Ÿซถ by installing files with owner and group attributes set to that of the user running the make(1) command. Bestie you still gotta set the DESTDIR variable to point at a directory where your user has write permissions, no cap. Permission check, slay, then install.
  • WITHOUT_IPFILTER โ€” do not build the IP Filter package. Not the vibe today, skip it โœจ
  • WITH_IPFILTER_IPFS โ€” enables building the ipfs(8) tool so you can save and restore IPFilter state tables. Save your state, restore your state, iconic ๐Ÿ’…
  • WITHOUT_IPFW โ€” do not build the IPFW tools. That's it, that's the whole flag ๐ŸŽ€
  • WITHOUT_IPSEC_SUPPORT โ€” do not build the kernel with ipsec(4) support. This option is needed for ipsec(4) and tcpmd5(4), so if you turn it off, those two are lowkey not coming to the party ๐Ÿ˜ญ
  • WITHOUT_ISCSI โ€” do not build iscsid(8) and all its related utilities. Bye-bye iSCSI besties ๐Ÿ‘‹
  • WITHOUT_JAIL โ€” do not build the tools for the support of jails, e.g., jail(8). If you love confinement (affectionate), don't set this fr fr ๐Ÿ”’
  • WITHOUT_JEMALLOC_LG_VADDR_WIDE โ€” disallows programs from using more than 48 address bits on amd64. It's incompatible with LA57 mode. Turning this on might give you a slight reduction in memory consumption for jemalloc metadata, but it also requires disabling LA57 (if your hardware even supports it). Tradeoffs, bestie, tradeoffs ๐Ÿ’€
  • WITHOUT_KDUMP โ€” do not build kdump(1) and truss(1). No crash-dump translating, no syscall tracing, we simply don't look ๐Ÿ‘‘๐Ÿ™ˆ
  • WITHOUT_KERBEROS โ€” set this and Kerberos does not get built. When it's set, this option is also in effect:
    • WITHOUT_KERBEROS_SUPPORT (unless WITH_KERBEROS_SUPPORT is set explicitly)
  • WITHOUT_KERBEROS_SUPPORT โ€” build some programs without Kerberos support, like ssh(1), telnet(1), and sshd(8). They still work, they just don't get the Kerberos glow-up โœจ
  • WITH_KERNEL_BIN โ€” generate and install kernel.bin from the kernel as part of the normal build and install processes for the kernel. Available only on arm and arm64 ๐Ÿฆ‹

Usually this gets added to the kernel config file with:

makeoptions    WITH_KERNEL_BIN=1

though it can also be used on the command line. Either way, she's flexible, we love that ๐Ÿ’–

  • WITH_KERNEL_RETPOLINE โ€” enables the "retpoline" mitigation for CVE-2017-5715 in the kernel build. Security said main character energy ๐Ÿ”ฅ
  • WITHOUT_KERNEL_SYMBOLS โ€” do not install the standalone kernel debug symbol files. Heads up: this option has no effect at build time โญ
  • WITHOUT_KVM โ€” do not build the libkvm library as a part of the base system. The option has no effect yet (I know, I know ๐Ÿ˜ญ). When it's set, this option is also in effect:
    • WITHOUT_KVM_SUPPORT (unless WITH_KVM_SUPPORT is set explicitly)
  • WITHOUT_KVM_SUPPORT โ€” build some programs without the optional libkvm support. Same programs, lighter bag ๐Ÿ’…
  • WITHOUT_LDNS โ€” setting this variable prevents the LDNS library from being built. When it's set, it enforces these options:
    • WITHOUT_LDNS_UTILS
    • WITHOUT_UNBOUND

Honestly it's giving "one decision, three consequences" ๐ŸŒธ

  • WITHOUT_LDNS_UTILS โ€” setting this variable prevents building the LDNS utilities drill(1) and host(1). No dig energy from these two ๐ŸŽ€
  • WITHOUT_LEGACY_CONSOLE โ€” do not build the programs that support a legacy PC console, e.g., kbdcontrol(1) and vidcontrol(1). She's retired, respect her ๐Ÿ’œ
  • WITHOUT_LIB32 โ€” on 64-bit platforms, do not build the 32-bit library set and a ld-elf32.so.1 runtime linker.

This is a default setting on arm/armv7, i386/i386, powerpc/powerpc64le and riscv/riscv64.

  • WITH_LIB32 โ€” on 64-bit platforms, build the 32-bit library set and a ld-elf32.so.1 runtime linker. The 32-bit girlies are so back ๐Ÿฆ‹

This is a default setting on amd64/amd64, arm64/aarch64 and powerpc/powerpc64.

  • WITHOUT_LLD โ€” do not build LLVM's lld linker. LLD said "I'm leaving" ๐Ÿ’€
  • WITHOUT_LLDB โ€” do not build the LLDB debugger. No breakpoints, no stepping through code, no nosy bestie energy ๐Ÿ™ˆ

This is a default setting on riscv/riscv64.

  • WITH_LLDB โ€” build the LLDB debugger. Now with the nosy bestie energy ๐Ÿ”ฅ

This is a default setting on amd64/amd64, arm/armv7, arm64/aarch64, i386/i386, powerpc/powerpc64 and powerpc/powerpc64le.

  • WITHOUT_LLD_BOOTSTRAP โ€” do not build the LLD linker during the bootstrap phase of the build. To be able to build the system, an alternate linker must be provided via XLD โš ๏ธ like, you must, not optional.
  • WITH_LLVM_ASSERTIONS โ€” enable debugging assertions in LLVM. She checks everything twice and I respect it โœจ
  • WITHOUT_LLVM_BINUTILS โ€” install ELF Tool Chain's binary utilities instead of LLVM's. This includes addr2line(1), ar(1), nm(1), objcopy(1), ranlib(1), readelf(1), size(1), and strip(1). Regardless of this setting, LLVM tools are used for c++filt(1) and objdump(1). And strings(1) is always provided by ELF Tool Chain โ€” that one's not up for debate ๐Ÿ‘‘
  • WITHOUT_LLVM_COV โ€” do not build the llvm-cov(1) tool. Coverage? Not today ๐Ÿ’…
  • WITHOUT_LLVM_CXXFILT โ€” install ELF Tool Chain's cxxfilt as c++filt, instead of LLVM's llvm-cxxfilt. Same name, different girlie ๐ŸŽ€
  • WITH_LLVM_FULL_DEBUGINFO โ€” generate full debug information for LLVM libraries and tools. It uses more disk space and build resources, but it allows for easier debugging. Expensive but worth it, ykyk ๐Ÿ’ธ๐Ÿ’–
  • WITH_LLVM_LINK_STATIC_LIBRARIES โ€” link the LLVM libraries (libllvm, libclang, liblldb) statically into each of the binaries that use them.

This means binaries linked against these libraries, such as clang, ld.lld and lldb, will be much larger and position dependent โ€” but they will start more quickly. Big girlies, fast girlies โญ

  • WITHOUT_LLVM_TARGET_AARCH64 โ€” do not build LLVM target support for AArch64. The LLVM_TARGET_ALL option should be used rather than this in most cases. (Read: don't do this manually, bestie.)
  • WITHOUT_LLVM_TARGET_ALL โ€” only build the required LLVM target support. This option is preferred to the specific target support options. When it's set, these options are also in effect:
    • WITHOUT_LLVM_TARGET_AARCH64 (unless WITH_LLVM_TARGET_AARCH64 is set explicitly)
    • WITHOUT_LLVM_TARGET_ARM (unless WITH_LLVM_TARGET_ARM is set explicitly)
    • WITHOUT_LLVM_TARGET_POWERPC (unless WITH_LLVM_TARGET_POWERPC is set explicitly)
    • WITHOUT_LLVM_TARGET_RISCV (unless WITH_LLVM_TARGET_RISCV is set explicitly)

One flag to rule them all, periodt ๐Ÿ‘‘

  • WITHOUT_LLVM_TARGET_ARM โ€” do not build LLVM target support for ARM. The LLVM_TARGET_ALL option should be used rather than this in most cases.
  • WITH_LLVM_TARGET_BPF โ€” build LLVM target support for BPF. The LLVM_TARGET_ALL option should be used rather than this in most cases.
  • WITH_LLVM_TARGET_MIPS โ€” build LLVM target support for MIPS. The LLVM_TARGET_ALL option should be used rather than this in most cases.
  • WITHOUT_LLVM_TARGET_POWERPC โ€” do not build LLVM target support for PowerPC. The LLVM_TARGET_ALL option should be used rather than this in most cases.
  • WITHOUT_LLVM_TARGET_RISCV โ€” do not build LLVM target support for RISC-V. The LLVM_TARGET_ALL option should be used rather than this in most cases.
  • WITHOUT_LLVM_TARGET_X86 โ€” do not build LLVM target support for X86. The LLVM_TARGET_ALL option should be used rather than this in most cases.

  • WITHOUT_LOADER_BIOS_TEXTONLY โ€” include graphics, font and video mode support in the i386 and amd64 BIOS boot loader. (Yes, that's the description for the WITHOUT_ version as written, bestie โ€” I don't make the rules ๐Ÿ’€)
  • WITH_LOADER_EFI_SECUREBOOT โ€” enable building loader(8) with support for verification based on certificates obtained from UEFI. Certificates only, we trust the vibes ๐ŸŒˆ๐Ÿ”
  • WITHOUT_LOADER_GELI โ€” disable inclusion of GELI crypto support in the boot chain binaries. No crypto at boot for you ๐ŸŽ€

This is a default setting on powerpc/powerpc64 and powerpc/powerpc64le.

  • WITH_LOADER_GELI โ€” build GELI bootloader support. Crypto at boot, slay ๐Ÿ’…

This is a default setting on amd64/amd64, arm/armv7, arm64/aarch64, i386/i386 and riscv/riscv64.

  • WITHOUT_LOADER_IA32 โ€” do not build the 32-bit UEFI loader.

This is a default setting on arm/armv7, arm64/aarch64, i386/i386, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.

  • WITH_LOADER_IA32 โ€” build the 32-bit UEFI loader. Tiny loader, huge heart ๐Ÿฆ‹

This is a default setting on amd64/amd64.

  • WITHOUT_LOADER_KBOOT โ€” do not build kboot, a linuxboot environment loader. (Note: no trailing period in the original description, and I respect the chaos ๐Ÿ˜Œ)

This is a default setting on arm/armv7, i386/i386, powerpc/powerpc64le and riscv/riscv64.

  • WITH_LOADER_KBOOT โ€” build kboot, a linuxboot environment loader

This is a default setting on amd64/amd64, arm64/aarch64 and powerpc/powerpc64.

  • WITHOUT_LOADER_LUA โ€” do not build LUA bindings for the boot loader. Scripting said "not my era" ๐Ÿ’€

This is a default setting on powerpc/powerpc64 and powerpc/powerpc64le.

  • WITH_LOADER_LUA โ€” build LUA bindings for the boot loader. Boot-time scripting is such a vibe โœจ

This is a default setting on amd64/amd64, arm/armv7, arm64/aarch64, i386/i386 and riscv/riscv64.

  • WITHOUT_LOADER_OFW โ€” disable building of openfirmware bootloader components.

This is a default setting on amd64/amd64, arm/armv7, arm64/aarch64, i386/i386 and riscv/riscv64.

  • WITH_LOADER_OFW โ€” build openfirmware bootloader components.

This is a default setting on powerpc/powerpc64 and powerpc/powerpc64le.

  • WITHOUT_LOADER_PXEBOOT โ€” do not build pxeboot on i386/amd64. When the pxeboot is too large, or unneeded, it may be disabled with this option. See WITH_LOADER_PXEBOOT for how to adjust the defaults when you need both a larger /boot/loader and /boot/pxeboot ๐Ÿซถ
Heads up: this option only has an effect on x86. Everywhere else it's just decorative ๐Ÿ’…
  • WITHOUT_LOADER_UBOOT โ€” disable building of ubldr.

This is a default setting on amd64/amd64, arm64/aarch64, i386/i386, powerpc/powerpc64le and riscv/riscv64.

  • WITH_LOADER_UBOOT โ€” build ubldr. She's back, she's booting ๐Ÿฆ‹

This is a default setting on arm/armv7 and powerpc/powerpc64.

  • WITH_LOADER_VERBOSE โ€” build with extra verbose debugging in the loader. May explode an already nearly-too-large loader over the limit. Use with care โš ๏ธ like genuinely, she's already at capacity, don't push her ๐Ÿ˜ญ
  • WITH_LOADER_VERIEXEC โ€” enable building loader(8) with support for verification similar to Verified Exec. Depends on WITH_BEARSSL. May require a larger LOADERSIZE. When it's set, these options are also in effect:
    • WITH_LOADER_EFI_SECUREBOOT (unless WITHOUT_LOADER_EFI_SECUREBOOT is set explicitly)
    • WITH_LOADER_VERIEXEC_VECTX (unless WITHOUT_LOADER_VERIEXEC_VECTX is set explicitly)

Verify everything, trust nothing ๐Ÿ’–

  • WITH_LOADER_VERIEXEC_PASS_MANIFEST โ€” enable building loader(8) with support to pass a verified manifest to the kernel. The kernel has to be built with a module to parse the manifest โ€” so this is a two-piece fit, no cap ๐Ÿงฉ

Depends on WITH_LOADER_VERIEXEC.

  • WITH_LOADER_VERIEXEC_VECTX โ€” enable building loader(8) with support for hashing and verifying the kernel and modules as a side effect of loading. Verification as a little treat, we love an efficient queen ๐Ÿ‘‘

Depends on WITH_LOADER_VERIEXEC ๐Ÿ’– (that's the tail of that last one, bestie, keep it attached to whichever entry came just above).

  • WITHOUT_LOADER_ZFS โ€” no ZFS file system boot loader support, sorry to the ZFS girlies ๐Ÿซถ
  • WITHOUT_LOCALES โ€” no localization files; peep locale(1) for the deets.
  • WITHOUT_LOCATE โ€” locate(1) and its little friends don't get built. Your locate era is over ๐Ÿ˜ญ
  • WITHOUT_LPR โ€” lpr(1) and friends, gone. No printing printcess here ๐Ÿ’…
  • WITHOUT_LS_COLORS โ€” you still get ls(1), just no color support for telling file types apart. Monochrome realness, lowkey sad ๐ŸŽ€
  • WITHOUT_MACHDEP_OPTIMIZATIONS โ€” prefer machine-independent, non-assembler code in libc and libm. Vibes = portable, not hand-tuned โœจ
  • WITHOUT_MAIL โ€” zero mail support at all, MUA or MTA, none of it ๐Ÿ“ญ When you set this, it also enforces:
    • WITHOUT_DMAGENT
    • WITHOUT_MAILWRAPPER
    • WITHOUT_SENDMAIL
  • WITHOUT_MAILWRAPPER โ€” skip the mailwrapper(8) MTA selector entirely.
  • WITHOUT_MAKE โ€” make(1) and related support files do not get installed. (Iconic, terrifying, moving on ๐Ÿ’€)
  • WITHOUT_MAKE_CHECK_USE_SANDBOX โ€” don't run โ€œmake checkโ€ in limited sandbox mode. Pair this with WITH_INSTALL_AS_USER if you're running it as an unprivileged user โ€” that part matters, fr fr. See tests(7) for the full lore ๐Ÿฆ‹
  • WITHOUT_MALLOC_PRODUCTION โ€” this one turns on the extra stuff: assertions and statistics gathering in malloc(3). The run-time options opt.abort, opt.abort_conf, and opt.junk also default to true ๐Ÿงš (yes, WITHOUT_ enabling things is giving chaos, that's just how it is)
  • WITHOUT_MAN โ€” no manual pages get built. When set, this is also in effect:
    • WITHOUT_MAN_UTILS (unless WITH_MAN_UTILS is set explicitly)
  • WITHOUT_MANCOMPRESS โ€” no compressed man pages installed; only the uncompressed versions go in. Unzipped and unbothered ๐ŸŒธ
  • WITH_MANSPLITPKG โ€” split man pages into their own packages during make package. So organized ๐Ÿ’–
  • WITHOUT_MAN_UTILS โ€” no utilities for manual pages: apropos(1), makewhatis(1), man(1), whatis(1), manctl(8), and related support files. The whole help-me-find-help squad, gone ๐Ÿ™ˆ
  • WITH_META_ERROR_TARGET โ€” enables the META_MODE .ERROR target. This target copies the meta file of a failed target into ERROR_LOGDIR (default is ${SRCTOP:H}/error) so you can do failure analysis later. Depends on WITH_META_MODE. It's the default when WITH_DIRDEPS_BUILD is set ๐Ÿ•ต๏ธ
Heads up bestie: this must be set in the environment, on the make command line, or in /etc/src-env.conf โ€” not in /etc/src.conf. Not negotiable.
  • WITH_META_MODE โ€” creates make(1) meta files while building, which can give you a reliable incremental build when you're using filemon(4). The meta file lands in OBJDIR as target.meta โœจ These meta files track the command that was executed, its output, and the current directory. The filemon(4) module is required unless NO_FILEMON is defined. Once the module is loaded, any files used by the commands you executed get tracked as dependencies for that target in its meta file. A target counts as out-of-date and gets rebuilt if any of these are true compared to the last build:
    • The command to execute changes.
    • The current working directory changes.
    • The target's meta file is missing.
    • The target's meta file is missing filemon data when filemon is loaded and a previous run did not have it loaded.
    • [requires filemon(4)] Files read, executed or linked to are newer than the target.
    • [requires filemon(4)] Files read, written, executed or linked are missing.

The meta files can also be useful for debugging ๐Ÿ‘‘ The build hides commands that are executed unless NO_SILENT is defined. Errors cause make(1) to show some of its environment so you can debug further. The build operates as it normally would otherwise. This option originally invoked a different build system, but that got renamed to WITH_DIRDEPS_BUILD.

Again for the people in the back: this must be set in the environment, on the make command line, or in /etc/src-env.conf, not /etc/src.conf ๐Ÿ’…
  • WITHOUT_MITKRB5 โ€” set this to build KTH Heimdal instead of MIT Kerberos 5. Pick your Kerberos fighter ๐ŸฅŠ
  • WITHOUT_MLX5TOOL โ€” no mlx5tool(8). This is a default setting on arm/armv7 and riscv/riscv64.
  • WITH_MLX5TOOL โ€” builds mlx5tool(8). This is a default setting on amd64/amd64, arm64/aarch64, i386/i386, powerpc/powerpc64 and powerpc/powerpc64le.
  • WITHOUT_NETCAT โ€” no nc(1) utility. (The netcat girlies are in shambles ๐Ÿ˜ญ)
  • WITHOUT_NETGRAPH โ€” no applications supporting netgraph(4). When set, it enforces:
    • WITHOUT_BLUETOOTH

And when set, these options are also in effect:

  • WITHOUT_NETGRAPH_SUPPORT (unless WITH_NETGRAPH_SUPPORT is set explicitly)
  • WITHOUT_NETGRAPH_SUPPORT โ€” build libraries, programs, and kernel modules without netgraph support.
  • WITHOUT_NETLINK โ€” no genl(1) utility.
  • WITHOUT_NETLINK_SUPPORT โ€” make libraries and programs use rtsock and sysctl(3) interfaces instead of snl(3). Old school, but make it fashion ๐Ÿ’…
  • WITHOUT_NIS โ€” no NIS(8) support and related programs. If you set this, you might need to adopt your nsswitch.conf(5) and remove โ€˜nisโ€™ entries. Do the cleanup, bestie ๐Ÿงน
  • WITHOUT_NLS โ€” no NLS catalogs at all. When set, it enforces:
    • WITHOUT_NLS_CATALOGS
  • WITHOUT_NLS_CATALOGS โ€” no NLS catalog support for csh(1). ๐Ÿš
  • WITHOUT_NS_CACHING โ€” disables name caching in the nsswitch subsystem. The generic caching daemon, nscd(8), won't be built either if this is set. No cache, only vibes โญ
  • WITHOUT_NTP โ€” no ntpd(8) and related programs. Time is a construct anyway ๐Ÿ•ฐ๏ธ
  • WITHOUT_NUAGEINIT โ€” don't install the limited cloud init support scripts.
  • WITHOUT_OFED โ€” no โ€œOpenFabrics Enterprise Distributionโ€ InfiniBand software stack, including kernel modules and userspace libraries. This is a default setting on arm/armv7. When set, it enforces:
    • WITHOUT_OFED_EXTRA
  • WITH_OFED โ€” builds the โ€œOpenFabrics Enterprise Distributionโ€ InfiniBand software stack, including kernel modules and userspace libraries. This is a default setting on amd64/amd64, arm64/aarch64, i386/i386, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.
  • WITH_OFED_EXTRA โ€” builds the non-essential components of the โ€œOpenFabrics Enterprise Distributionโ€ Infiniband software stack, mostly examples. The bonus content ๐ŸŽ€
  • WITH_OPENLDAP โ€” enables building LDAP support for kerberos using an openldap client from ports.
  • WITHOUT_OPENMP โ€” no LLVM's OpenMP runtime. This is a default setting on arm/armv7.
  • WITH_OPENMP โ€” builds LLVM's OpenMP runtime. This is a default setting on amd64/amd64, arm64/aarch64, i386/i386, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.
  • WITHOUT_OPENSSH โ€” no OpenSSH. No cap, that's a big one ๐Ÿซถ
  • WITHOUT_OPENSSL โ€” no OpenSSL. When set, it enforces all of these:
    • WITHOUT_DMAGENT
    • WITHOUT_KERBEROS
    • WITHOUT_LDNS
    • WITHOUT_LDNS_UTILS
    • WITHOUT_LOADER_ZFS
    • WITHOUT_MITKRB5
    • WITHOUT_OPENSSH
    • WITHOUT_OPENSSL_KTLS
    • WITHOUT_PKGBOOTSTRAP
    • WITHOUT_UNBOUND
    • WITHOUT_ZFS
    • WITHOUT_ZFS_TESTS

When set, these options are also in effect:

  • WITHOUT_KERBEROS_SUPPORT (unless WITH_KERBEROS_SUPPORT is set explicitly)
  • WITHOUT_OPENSSL_KTLS โ€” don't include kernel TLS support in OpenSSL. This is a default setting on arm/armv7, i386/i386 and riscv/riscv64.
  • WITH_OPENSSL_KTLS โ€” includes kernel TLS support in OpenSSL. This is a default setting on amd64/amd64, arm64/aarch64, powerpc/powerpc64 and powerpc/powerpc64le.
  • WITHOUT_PAM โ€” don't build the PAM library and modules. โš ๏ธ Heads up: this option is deprecated and does nothing. When set, these options are also in effect:
    • WITHOUT_PAM_SUPPORT (unless WITH_PAM_SUPPORT is set explicitly)
  • WITHOUT_PAM_SUPPORT โ€” build ppp(8) without PAM support.
  • WITHOUT_PF โ€” no PF firewall package. When set, it enforces:
    • WITHOUT_AUTHPF
  • WITHOUT_PIE โ€” don't build dynamically linked binaries as Position-Independent Executable (PIE). This is a default setting on arm/armv7 and i386/i386.
  • WITH_PIE โ€” builds dynamically linked binaries as Position-Independent Executable (PIE). This is a default setting on amd64/amd64, arm64/aarch64, powerpc/powerpc64, powerpc/powerpc64le and riscv/riscv64.
  • WITHOUT_PKGBOOTSTRAP โ€” no pkg(7) bootstrap tool.
  • WITHOUT_PMC โ€” no pmccontrol(8) and related programs.
  • WITHOUT_PPP โ€” no ppp(8) and related programs.
  • WITH_PTHREADS_ASSERTIONS โ€” enable debugging assertions in the pthreads library. Debug girl summer ๐Ÿ”ฅ
  • WITHOUT_QUOTAS โ€” no quota(1) and related programs.
  • WITHOUT_RADIUS_SUPPORT โ€” don't build radius support into various applications, like pam_radius(8) and ppp(8).
  • WITH_RATELIMIT โ€” builds the system with rate limit support. This makes SO_MAX_PACING_RATE effective in getsockopt(2), and gives you txrlimit support in ifconfig(8), by proxy. Throttle era โœจ
  • WITHOUT_RBOOTD โ€” don't build or install rbootd(8).
  • WITHOUT_RELRO โ€” don't apply the Relocation Read-Only (RELRO) vulnerability mitigation. โš ๏ธ That's a security mitigation, bestie โ€” see also the BIND_NOW option.
  • WITHOUT_REPRODUCIBLE_BUILD โ€” include build metadata (such as the build time, user, and host) in the kernel, boot loaders, and uname output. Successive builds will not be bit-for-bit identical. So much for twins ๐Ÿ’€
  • WITHOUT_RESCUE โ€” no rescue(8). Hope you don't need saving ๐Ÿ™ˆ
  • WITH_RETPOLINE โ€” builds the base system with the retpoline speculative execution vulnerability mitigation for CVE-2017-5715. Security slay ๐Ÿ›ก๏ธ
  • WITHOUT_ROUTED โ€” no routed(8) utility.
  • WITH_RPCBIND_WARMSTART_SUPPORT โ€” builds rpcbind(8) with warmstart support.
  • WITH_RUN_TESTS โ€” run tests as part of the build. Test-driven bestie behavior ๐Ÿ’–
  • WITHOUT_SCTP_SUPPORT โ€” disables kernel support for the sctp(4) Stream Control Transmission Protocol loadable kernel module.
  • WITHOUT_SENDMAIL โ€” no sendmail(8) and related programs. ๐Ÿ“ฎ
  • WITHOUT_SERVICESDB โ€” bestie, we are simply not installing /var/db/services.db. that's it, that's the whole vibe ๐Ÿ’…
  • WITHOUT_SETUID_LOGIN โ€” set this and login(1) does not get installed as a set-user-ID root program. no root-flavored login for you ๐Ÿซถ
  • WITHOUT_SHAREDOCS โ€” do not build the 4.4BSD legacy docs. they're giving ancient, lowkey, and we're not building them โœจ
  • WITH_SORT_THREADS โ€” turn on threads in sort(1). parallel sorting rights ๐Ÿ”ฅ
  • WITHOUT_SOUND โ€” do not build userland sound utilities like beep(1) and `mixer(8). it's a silent build, literally ๐Ÿฆ‹
  • WITHOUT_SOURCELESS โ€” do not build kernel modules that include sourceless code (either microcode or native code for host CPU). when this is set, it enforces these options:
    • WITHOUT_SOURCELESS_HOST
    • WITHOUT_SOURCELESS_UCODE
  • WITHOUT_SOURCELESS_HOST โ€” do not build kernel modules that include sourceless native code for host CPU. nope, not those ๐Ÿซถ
  • WITHOUT_SOURCELESS_UCODE โ€” do not build kernel modules that include sourceless microcode. skipping the ucode modules, periodt ๐Ÿ’œ
  • WITHOUT_SPLIT_KERNEL_DEBUG โ€” do not build standalone kernel debug files. debug data (if it's enabled by the kernel configuration file) just gets included in the kernel and modules instead. when set, it enforces these options:
    • WITHOUT_KERNEL_SYMBOLS
  • WITHOUT_SSP โ€” do not build world with stack smashing protection. see mitigations(7) for the whole lore ๐Ÿ’€
  • WITH_STAGING โ€” enable staging of files to a stage tree. think of it as auto-install to DESTDIR but with some extra meta data so dependencies can actually be tracked โ€” it's giving organized main character energy ๐Ÿ‘‘. depends on WITH_DIRDEPS_BUILD. when set, these options are also in effect:
    • WITH_STAGING_MAN (unless WITHOUT_STAGING_MAN is set explicitly)
    • WITH_STAGING_PROG (unless WITHOUT_STAGING_PROG is set explicitly)
โš ๏ธ this must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf. read it again bestie, it matters ๐Ÿ™ˆ
  • WITH_STAGING_MAN โ€” enable staging of man pages to stage tree. the manuals are getting staged too ๐Ÿ’–
  • WITH_STAGING_PROG โ€” enable staging of PROGs to stage tree. yes girl, the progs ๐ŸŽ€
  • WITH_STALE_STAGED โ€” check staged files are not stale. freshness check, slay โœจ
  • WITHOUT_STATS โ€” neither build nor install library โ€œlibstatsโ€ and dependent binaries. no stats, no binaries that need stats ๐ŸŒธ
  • WITHOUT_SYSCONS โ€” do not build syscons(4) support files such as keyboard maps, fonts, and screen output maps. ngl that's a whole little bundle we're skipping ๐Ÿฆ‹
  • WITH_SYSROOT โ€” enable use of sysroot during build. depends on WITH_DIRDEPS_BUILD.
โš ๏ธ this must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf. iykyk ๐Ÿ’…
  • WITHOUT_SYSTEM_COMPILER โ€” do not opportunistically skip building a cross-compiler during the bootstrap phase of the build. so normally, if the currently installed compiler matches the planned bootstrap compiler type and revision, then it will not be built โ€” this option kills that little shortcut. important caveat: this does not prevent a compiler from being built for installation though, only for building one for the build itself. the WITHOUT_CLANG option controls that one ๐Ÿ‘‘
  • WITHOUT_SYSTEM_LINKER โ€” do not opportunistically skip building a cross-linker during the bootstrap phase of the build. normally, if the currently installed linker matches the planned bootstrap linker type and revision, then it will not be built. this does not prevent a linker from being built for installation though, only for building one for the build itself โ€” the WITHOUT_LLD option controls that.

this option is only relevant when WITH_LLD_BOOTSTRAP is set. only then, bestie ๐Ÿ”ฅ

  • WITHOUT_TALK โ€” do not build or install talk(1) and talkd(8). no talking in this build fr fr ๐Ÿ˜ญ
  • WITHOUT_TCP_WRAPPERS โ€” do not build or install tcpd(8), and related utilities. the wrappers are staying home ๐Ÿซถ
  • WITHOUT_TCSH โ€” do not build and install /bin/csh (which is tcsh(1), bestie, they're the same thing). bye bye csh ๐Ÿ’œ
  • WITHOUT_TELNET โ€” do not build telnet(1) and related programs. no telnet era for us ๐Ÿ™ˆ
  • WITHOUT_TESTS โ€” do not build nor install the FreeBSD Test Suite in /usr/tests/. see tests(7) for more details. this also disables the build of all test-related dependencies, including ATF. when set, it enforces these options:
    • WITHOUT_DTRACE_TESTS
    • WITHOUT_ZFS_TESTS

when set, these options are also in effect:

  • WITHOUT_GOOGLETEST (unless WITH_GOOGLETEST is set explicitly)
  • WITHOUT_TESTS_SUPPORT (unless WITH_TESTS_SUPPORT is set explicitly)
  • WITHOUT_TESTS_SUPPORT โ€” disable the build of all test-related dependencies, including ATF. when set, it enforces these options:
    • WITHOUT_GOOGLETEST
  • WITHOUT_TEXTPROC โ€” do not build programs used for text processing. no textproc girls allowed ๐Ÿ’…
  • WITHOUT_TFTP โ€” do not build or install tftp(1) and tftpd(8). skipping the file transfer duo ๐Ÿฆ‹
  • WITHOUT_TOOLCHAIN โ€” do not install programs used for program development, compilers, debuggers etc. when set, it enforces these options:
    • WITHOUT_CLANG
    • WITHOUT_CLANG_EXTRAS
    • WITHOUT_CLANG_FORMAT
    • WITHOUT_CLANG_FULL
    • WITHOUT_LLD
    • WITHOUT_LLDB
    • WITHOUT_LLVM_COV

when set, these options are also in effect:

  • WITHOUT_LLVM_BINUTILS (unless WITH_LLVM_BINUTILS is set explicitly)
  • WITH_UBSAN โ€” build the base system with Undefined Behavior Sanitizer (UBSan) to detect various kinds of undefined behavior at runtime. requires that Clang be used as the base system compiler and that the runtime support library is available. (yes, both, no exceptions ๐Ÿ’€)
  • WITHOUT_UNBOUND โ€” do not build unbound(8) and related programs. unbound is not bound to this build ๐ŸŒˆ
  • WITH_UNDEFINED_VERSION โ€” link libraries with --undefined-version which permits version maps to contain symbols that are not present in the library. ngl, if this is necessary to build a particular configuration, a bug is present and the configuration should be reported. it's giving red flag ๐Ÿšฉ
  • WITHOUT_UNIFIED_OBJDIR โ€” use the historical object directory format for build(7) targets. for native-builds and builds done directly in sub-directories the format of ${MAKEOBJDIRPREFIX}/${.CURDIR} is used, while for cross-builds ${MAKEOBJDIRPREFIX}/${TARGET}.${TARGET_ARCH}/${.CURDIR} is used.

this option is transitional and will be removed in a future version of FreeBSD, at which time WITH_UNIFIED_OBJDIR will be enabled permanently. so likeโ€ฆ enjoy it while it lasts bestie ๐Ÿ’€

โš ๏ธ this must be set in the environment, make command line, or /etc/src-env.conf, not /etc/src.conf. same rule as always ๐Ÿซถ
  • WITHOUT_USB โ€” do not build USB-related programs and libraries. unplugged. literally ๐Ÿ”Œ
  • WITHOUT_USB_GADGET_EXAMPLES โ€” do not build USB gadget kernel modules. no little gadget modules for you ๐ŸŒธ
  • WITHOUT_UTMPX โ€” do not build user accounting tools such as last(1), users(1), who(1), ac(8), lastlogin(8) and utx(8). so nobody knows who logged in. iconique ๐ŸŽ€
  • WITH_VERIEXEC โ€” enable building veriexec(8) which loads the contents of verified manifests into the kernel for use by mac_veriexec(4).

depends on WITH_BEARSSL. yes, that's a real dependency name, no i'm not kidding ๐Ÿป

  • WITHOUT_VI โ€” do not build and install vi, view, ex and related programs. no editor for you, go touch grass ๐ŸŒฑ โ€” jk, but the option's the option ๐Ÿ’…
  • WITHOUT_VT โ€” do not build vt(4) support files (fonts and keymaps). skipping the fonts AND the keymaps ๐Ÿฆ‹
  • WITHOUT_WARNS โ€” set this to not add warning flags to the compiler invocations. useful as a temporary workaround when code enters the tree which triggers warnings in environments that differ from the original developer. temporary, bestie, i said what i said ๐Ÿ™ˆ
  • WITHOUT_WERROR โ€” set this to not treat compiler warnings as errors. useful as a temporary workaround when working on fixing compiler warnings. when set, warnings are still printed in the build log but do not fail the build. so it's a "we see you, we're just not mad about it" situation โœจ
  • WITHOUT_WIRELESS โ€” do not build programs used for 802.11 wireless networks; especially wpa_supplicant(8) and hostapd(8). when set, these options are also in effect:
    • WITHOUT_WIRELESS_SUPPORT (unless WITH_WIRELESS_SUPPORT is set explicitly)
  • WITHOUT_WIRELESS_SUPPORT โ€” build libraries, programs, and kernel modules without 802.11 wireless support. the whole build is going airplane mode โœˆ๏ธ
  • WITHOUT_WPA_SUPPLICANT_EAPOL โ€” build wpa_supplicant(8) without support for the IEEE 802.1X protocol and without support for EAP-PEAP, EAP-TLS, EAP-LEAP, and EAP-TTLS protocols (usable only via 802.1X). so many acronyms gone at once ๐Ÿ˜ญ
  • WITH_ZEROREGS โ€” build the basesystem with code to zero caller-used register contents on function return. this prevents leaking temporary values for side channel attacks. additionally this reduces the number of usable ROP gadgets for attackers. security girl summer ๐Ÿ”ฅ
  • WITHOUT_ZFS โ€” do not build the ZFS file system kernel module, libraries such as libbe(3), and user commands such as zpool(8) or zfs(8). also disable ZFS support in utilities and libraries which implement ZFS-specific functionality. when set, it enforces these options:
    • WITHOUT_ZFS_TESTS
  • WITHOUT_ZFS_TESTS โ€” do not build and install the legacy ZFS test suite. legacy tests, we hardly knew ye ๐Ÿฆ‹
  • WITHOUT_ZONEINFO โ€” do not build the timezone database. when set, it enforces these options:
    • WITHOUT_ZONEINFO_LEAPSECONDS_SUPPORT
  • WITH_ZONEINFO_LEAPSECONDS_SUPPORT โ€” build leapsecond information in to the timezone database.
๐Ÿšจ serious one, bestie โ€” this option violates IEEE Std 1003.1 (โ€œPOSIX.1โ€) and all other applicable standards, and is known to cause unexpected issues with date/time handling in many applications and programming languages. like, actually chaotic ๐Ÿ’€

the following options accept a single value from a list of valid values. one value. one. not a boolean situation ๐Ÿ‘‘

๐Ÿ’œ INIT_ALL

control default initialization of stack variables in C and C++ code. options other than none require the Clang compiler or GCC 12.0 or later. the default value is none. valid values are:

  • none โ€” do not initialize stack variables (standard C/C++ behavior). the classic ๐ŸŽ€
  • pattern โ€” build the base system or kernel with stack variables initialized to (compiler defined) debugging patterns on function entry.
  • zero โ€” build the base system or kernel with stack variables initialized to zero on function entry. heads up: this value is converted to none for amd64 kernel builds due to incompatibility with ifunc memset. so on amd64 it's giving "zero" but it's actually "none" ๐Ÿ™ˆ

๐Ÿ“ LIBC_MALLOC

specify the malloc(3) implementation used by libc. the default value is jemalloc. valid values are:

  • jemalloc

other implementations are expected in the future in both FreeBSD and downstream consumers. watch this space โœจ


๐ŸŽ€ FILES ๐ŸŽ€

  • /etc/src.conf
  • /etc/src-env.conf
  • /usr/share/mk/bsd.own.mk

๐Ÿซถ SEE ALSO

okay so like, if you wanna go deeper (and honestly? you should, bestie, the lore is rich), go peek at these:

  • make(1) โ€” the whole reason this file even matters, the main character fr
  • make.conf(5) โ€” its louder, more chaotic sibling โœจ
  • build(7) โ€” the big-picture overview of how the build system works
  • ports(7) โ€” for when you're off building ports and living your best life ๐ŸŽ€

๐ŸŒธ HISTORY

ngl this one's got a little origin story: the src.conf file made its debut in FreeBSD 7.0. iconic behavior, honestly. ๐Ÿ‘‘


๐Ÿ’… AUTHORS

and who do we have to thank for this masterpiece? plot twist: nobody hand-wrote it ๐Ÿ˜ญ this manual page was autogenerated by tools/build/options/makeman. so like, a script wrote it, which is lowkey the most Unix thing ever โ€” the machine documenting itself. main character energy fr fr ๐Ÿค–โœจ


aww okay bestie that's the whole page, you made it!! ๐ŸŽ‰ go forth and src.conf responsibly. mwah ๐Ÿ’–

โ€” signed, sealed, delivered: Debian build, dated March 28, 2026, brought to you by the fine folks behind SRC.CONF(5) ๐Ÿฆ‹

๐Ÿ“ฆ where this page comes from