xref: /src/share/mk/bsd.README

#	$NetBSD: bsd.README,v 1.444 2023/06/05 22:36:58 lukem Exp $
#	@(#)bsd.README	8.2 (Berkeley) 4/2/94

This is the README file for the make "include" files for the NetBSD
source tree.  The files are installed in /usr/share/mk, and are,
by convention, named with the suffix ".mk".

Other sources of relevant documentation are BUILDING in the top
level of the NetBSD source tree, and the mk.conf(5) man page.

Note: this file is not intended to replace reading through the .mk
files for anything tricky.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

RANDOM THINGS WORTH KNOWING:

The files are simply C-style #include files, and pretty much behave like
you'd expect.  The syntax is slightly different in that a single '.' is
used instead of the hash mark, i.e. ".include <bsd.prog.mk>".

One difference that will save you lots of debugging time is that inclusion
of the file is normally done at the *end* of the Makefile.  The reason for
this is because .mk files often modify variables and behavior based on the
values of variables set in the Makefile.  To make this work, remember that
the FIRST target found is the target that is used, i.e. if the Makefile has:

	a:
		echo a
	a:
		echo a number two

the command "make a" will echo "a".  To make things confusing, the SECOND
variable assignment is the overriding one, i.e. if the Makefile has:

	a=	foo
	a=	bar

	b:
		echo ${a}

the command "make b" will echo "bar".  This is for compatibility with the
way the V7 make behaved.

It's fairly difficult to make the BSD .mk files work when you're building
multiple programs in a single directory.  It's a lot easier to split up the
programs than to deal with the problem.  Most of the agony comes from making
the "obj" directory stuff work right, not because we switched to a new version
of make.  So, don't get mad at us, figure out a better way to handle multiple
architectures so we can quit using the symbolic link stuff.  (Imake doesn't
count.)

The file .depend in the source directory is expected to contain dependencies
for the source files.  This file is read automatically by make after reading
the Makefile.

The variable DESTDIR works as before.  It's not set anywhere but will change
the tree where the file gets installed.

The profiled libraries are no longer built in a different directory than
the regular libraries.  A new suffix, ".po", is used to denote a profiled
object, and ".pico" denotes a shared (position-independent) object.

There are various make variables used during the build.

Many variables support a (case sensitive) value of "no" or "yes",
and are tested with  ${VAR} == "no"  and  ${VAR} != "no" .


The basic rule for the variable naming scheme is as follows:

HOST_<cmd>	A command that runs on the host machine regardless of
		whether or not the system is being cross compiled, or
		flags for such a command.

MK<feature>	Can be set to "no" to disable feature <feature>,
		or "yes" to enable feature <feature>.
		Usually defaults to "yes", although some variables
		default to "no".
		Due to make(1) implementation issues, if a temporary
		command-line override of a mk.conf(5) or <bsd.own.mk>
		setting is required whilst still honoring a particular
		Makefile's setting of MK<feature>, use
			env MK<feature>=value make
		instead of
			make MK<feature>=value

NO<feature>	If defined, disables feature <feature>, overriding
		a user's MK<feature>=yes configuration.
		Not intended for users.
		This is to allow Makefiles to disable functionality
		that they don't support (such as missing man pages).
		NO<feature> variables must be defined before <bsd.own.mk>
		is included, which generally means define before
		any <*.mk> is included.
		See "Variables for a Makefile".

TOOL_<tool>	A tool that is provided as part of the USETOOLS
		framework.  When not using the USETOOLS framework,
		TOOL_<tool> variables should refer to tools that are
		already installed on the host system.

The following variables control how things are made/installed that
are not set by default. These should not be set by Makefiles; they're for
the user to define in MAKECONF (see <bsd.own.mk>, below, or mk.conf(5))
or on the make(1) command line:

BUILD		If defined, 'make install' checks that the targets in the
		source directories are up-to-date and re-makes them if
		they are out of date, instead of blindly trying to
		install out of date or non-existent targets.

		Default: Unset.

BUILDID		Identifier for the build.  If set, this should be a short
		string that is suitable for use as part of a file or
		directory name.  The identifier will be appended to
		object directory names, and can be consulted in the
		make(1) configuration file in order to set additional
		build parameters, such as compiler flags.  It will also
		be used as part of the kernel version string, which can
		be shown by "uname -v".

		Default: Unset.

BUILDINFO	Optional multi-line string containing information about
		the build.  This will appear in DESTDIR/etc/release, and
		it will be stored in the buildinfo variable in any
		kernels that are built.  When such kernels are booted,
		the sysctl(7) kern.buildinfo variable will report this
		value.  The string may contain backslash escape
		sequences, such as "\\" (representing a backslash
		character) and "\n" (representing a newline).

		Default: Unset.

BUILDSEED	g++(1) uses random numbers when compiling C++ code.  This
		variable seeds the g++(1) random number generator using
		-frandom-seed with this value.  By default, it is set to
		"NetBSD-(majorversion)".  Using a fixed value causes C++
		binaries to be the same when built from the same sources,
		resulting in identical (reproducible) builds.  Additional
		information is available in the g++(1) documentation of
		-frandom-seed.

		Default: Unset.

MAKEVERBOSE	Level of verbosity of status messages.  Supported values:

		0   No descriptive messages or commands executed by
		    make(1) are shown.

		1   Brief messages are shown describing what is being
		    done, but the actual commands executed by make(1) are
		    not displayed.

		2   Descriptive messages are shown as above (prefixed
		    with a `#'), and ordinary commands performed by
		    make(1) are displayed.

		3   In addition to the above, all commands performed by
		    make(1) are displayed, even if they would ordinarily
		    have been hidden through use of the "@" prefix in the
		    relevant makefile.

		4   In addition to the above, commands executed by
		    make(1) are traced through use of the sh(1) "-x"
		    flag.

		Default: 2

MKAMDGPUFIRMWARE
		Can be set to "yes" or "no".  Indicates whether to
		install the /libdata/firmware/amdgpu directory, which is
		necessary for the amdgpu(4) AMD RADEON GPU video driver.

		Default: "yes" on i386 and x86_64; "no" on other
		platforms.

MKARGON2	Can be set to "yes" or "no".  Indicates whether the
		Argon2 hash is enabled in libcrypt.

		Default: "yes"

MKARZERO	Can be set to "yes" or "no".  Indicates whether ar(1)
		should zero the timestamp, uid, and gid in the archive
		for reproducible builds.

		Default: The value of MKREPRO (if defined), otherwise
		"no".

MKATF		Can be set to "yes" or "no".  Indicates whether the
		Automated Testing Framework (ATF) will be built and
		installed.  This also controls whether the NetBSD test
		suite will be built and installed, as the tests rely on
		ATF and cannot be built without it.

		Forced to "no" if MKCXX=no.

		Default: "yes"

MKBFD		Obsolete, use MKBINUTILS.

MKBINUTILS	Can be set to "yes" or "no".  Indicates whether any of
		the binutils tools or libraries will be built and
		installed.  That is, the libraries libbfd, libiberty, or
		any of the things that depend upon them, e.g.  as(1),
		ld(1), dbsym(8), or mdsetimage(8).

		Forced to "no" if TOOLCHAIN_MISSING!=no.

		Default: "yes"

MKBSDGREP	Can be set to "yes" or "no".  Determines which
		implementation of grep(1) will be built and installed.
		If "yes", use the BSD implementation.  If "no", use the
		GNU implementation.

		Default: "no"

MKBSDTAR	Can be set to "yes" or "no".  Determines which
		implementation of cpio(1) and tar(1) will be built and
		installed.  If "yes", use the libarchive-based
		implementations.  If "no", use the pax(1) based
		implementations.

		Default: "yes"

MKCATPAGES	Can be set to "yes" or "no".  Indicates whether
		preformatted plaintext manual pages will be created and
		installed.

		Forced to "no" if MKMAN=no or MKSHARE=no.

		Default: "no"

MKCLEANSRC	Can be set to "yes" or "no".  Indicates whether `make
		clean' and `make cleandir' will delete file names in
		CLEANFILES or CLEANDIRFILES from both the object
		directory, .OBJDIR, and the source directory, .SRCDIR.

		If "yes", then these file names will be deleted relative
		to both .OBJDIR and .CURDIR.  If "no", then the deletion
		will be performed relative to .OBJDIR only.

		Default: "yes"

MKCLEANVERIFY	Can be set to "yes" or "no".  Controls whether `make
		clean' and `make cleandir' will verify that files have
		been deleted.  If "yes", then file deletions will be
		verified using ls(1).  If "no", then file deletions will
		not be verified.

		Default: "yes"

MKCOMPAT	Can be set to "yes" or "no".  Indicates whether support
		for multiple ABIs is to be built and installed.

		Forced to "no" if NOCOMPAT is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "yes" on aarch64 (without gcc), mips64,
		powerpc64, riscv64, sparc64, and x86_64; "no" on other
		platforms.

MKCOMPATMODULES
		Can be set to "yes" or "no".  Indicates whether the
		compat kernel modules will be built and installed.

		Forced to "no" if MKCOMPAT=no.

		Default: "yes" on evbppc-powerpc and mips64; "no" on
		other platforms.

MKCOMPATTESTS	Can be set to "yes" or "no".  Indicates whether the
		NetBSD test suite for src/compat will be built and
		installed.

		Forced to "no" if MKCOMPAT=no.

		Default: "no"

MKCOMPATX11	Can be set to "yes" or "no".  Indicates whether the X11
		libraries will be built and installed.

		Forced to "no" if MKCOMPAT=no.

		Default: "no"

MKCOMPLEX	Can be set to "yes" or "no".  Indicates whether the Math
		Library (libm, -lm) is compiled with support for
		<complex.h>.

		Default: "yes"

MKCROSSGDB	Can be set to "yes" or "no".  Create a cross-gdb as a
		host tool.

		Default: "no"

MKCRYPTO	Obsolete.

MKCTF		Can be set to "yes" or "no".  Indicates whether CTF tools
		are to be built and installed.  If "yes", the tools will
		be used to generate and manipulate CTF data of ELF
		binaries during build.

		Forced to "no" if NOCTF is defined, usually in the
		Makefile before any make(1) .include directives.

		This is disabled internally for standalone programs in
		/usr/mdec.

		Default: "yes" on aarch64, amd64, and i386; "no" on other
		platforms.

MKCVS		Can be set to "yes" or "no".  Indicates whether cvs(1)
		will be built and installed.

		Default: "yes"

MKCXX		Can be set to "yes" or "no".  Indicates whether C++
		support is enabled.

		If "no", C++ compilers and software will not be built,
		and acts as MKATF=no MKGCCCMDS=no MKGDB=no MKGROFF=no
		MKKYUA=no.

		Default: "yes"

MKDEBUG		Can be set to "yes" or "no".  Indicates whether debug
		information should be generated for all userland
		binaries.  The result is collected as an additional
		debug.tgz and xdebug.tgz set and installed in
		DESTDIR/usr/libdata/debug.

		Forced to "no" if NODEBUG is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "no"

MKDEBUGKERNEL	Can be set to "yes" or "no".  Indicates whether debugging
		symbols will be built for kernels by default; pretend as
		if makeoptions DEBUG="-g" is specified in kernel
		configuration files.  This will also put the debug kernel
		netbsd.gdb in the kernel sets.  See options(4) for
		details.  This is useful if a cross-gdb is built as well
		(see MKCROSSGDB).

		Default: "no"

MKDEBUGLIB	Can be set to "yes" or "no".  Indicates whether debug
		libraries (lib*_g.a) will be built and installed.  Debug
		libraries are compiled with "-g -DDEBUG".

		Forced to "no" if NODEBUGLIB is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "no"

MKDEBUGTOOLS	Can be set to "yes" or "no".  Indicates whether debug
		information (lib*_g.a) will be included in the build
		toolchain.

		Default: "no"

MKDEPINCLUDES	Can be set to "yes" or "no".  Indicates whether to add
		.include statements in the .depend files instead of
		inlining the contents of the *.d files.  This is useful
		when stale dependencies are present, to list the exact
		files that need refreshing, but it is possibly slower
		than inlining.

		Default: "no"

MKDOC		Can be set to "yes" or "no".  Indicates whether system
		documentation destined for DESTDIR/usr/share/doc will be
		installed.

		Forced to "no" if NODOC is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKSHARE=no.

		Default: "yes"

MKDTB		Can be set to "yes" or "no".  Indicates whether the
		devicetree blobs will be built and installed.

		Default: "yes" on aarch64, armv6, armv7, riscv32, and
		riscv64; "no" on other platforms.

MKDTC		Can be set to "yes" or "no".  Indicates whether the
		Device Tree Compiler (dtc) will be built and installed.

		Default: "yes"

MKDTRACE	Can be set to "yes" or "no".  Indicates whether the
		kernel modules, utilities, and libraries for dtrace(1)
		support are to be built and installed.

		Default: "yes" on aarch64, amd64, and i386; "no" on other
		platforms.

MKDYNAMICROOT	Can be set to "yes" or "no".  Indicates whether all
		programs should be dynamically linked, and to install
		shared libraries required by /bin and /sbin and the
		shared linker ld.elf_so(1) into /lib.  If "no", link
		programs in /bin and /sbin statically.

		Default: "no" on ia64; "yes" on other platforms.

MKEXTSRC	Obsolete.

MKFIRMWARE	Can be set to "yes" or "no".  Indicates whether to
		install the /libdata/firmware directory, which is
		necessary for various drivers, including: athn(4),
		bcm43xx(4), bwfm(4), ipw(4), iwi(4), iwm(4), iwn(4),
		otus(4), ral(4), rtwn(4), rum(4), run(4), urtwn(4),
		wpi(4), zyd(4), and the Tegra 124 SoC.

		Default: "yes" on amd64, cobalt, evbarm, evbmips, evbppc,
		hpcarm, hppa, i386, mac68k, macppc, sandpoint, and
		sparc64; "no" on other platforms.

MKGCC		Can be set to "yes" or "no".  Indicates whether gcc(1) or
		any related libraries (libg2c, libgcc, libobjc,
		libstdc++) will be built and installed.

		Forced to "no" if TOOLCHAIN_MISSING!=no or
		EXTERNAL_TOOLCHAIN is defined.

		Default: "yes"

MKGCCCMDS	Can be set to "yes" or "no".  Indicates whether gcc(1)
		will be built and installed.  If "no", then MKGCC
		controls if the GCC libraries will be built and
		installed.

		Forced to "no" if MKCXX=no.

		Default: "no" on m68000; "yes" on other platforms.

MKGDB		Can be set to "yes" or "no".  Indicates whether gdb(1)
		will be built and installed.

		Forced to "no" if MKCXX=no or TOOLCHAIN_MISSING!=no.

		Default: "no" on ia64 and or1k; "yes" on other platforms.

MKGROFF		Can be set to "yes" or "no".  Indicates whether groff(1)
		will be built, installed, and used to format some of the
		PostScript and PDF documentation.

		Forced to "no" if MKCXX=no.

		Default: "yes"

MKGROFFHTMLDOC	Can be set to "yes" or "no".  Indicates whether to use
		groff(1) to generate HTML for miscellaneous articles
		which sometimes requires software not in the base
		installation.  Does not affect the generation of HTML man
		pages.

		Default: "no"

MKHESIOD	Can be set to "yes" or "no".  Indicates whether the
		Hesiod infrastructure (libraries and support programs)
		will be built and installed.

		Default: "yes"

MKHOSTOBJ	Can be set to "yes" or "no".  If "yes", then for programs
		intended to be run on the compile host, the name,
		release, and architecture of the host operating system
		will be suffixed to the name of the object directory
		created by "make obj".  (This allows multiple host
		systems to compile NetBSD for a single target.)	 If "no",
		then programs built to be run on the compile host will
		use the same object directory names as programs built to
		be run on the target.

		Default: "no"

MKHTML		Can be set to "yes" or "no".  Indicates whether the HTML
		manual pages are created and installed.

		Forced to "no" if NOHTML is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKMAN=no or MKSHARE=no.

		Default: "yes"

MKIEEEFP	Can be set to "yes" or "no".  Indicates whether code for
		IEEE754/IEC60559 conformance will be built and installed.
		Has no effect on most platforms.

		Default: "yes"

MKINET6		Can be set to "yes" or "no".  Indicates whether INET6
		(IPv6) infrastructure (libraries and support programs)
		will be built and installed.

		Note: MKINET6 must not be set to "no" if MKX11!=no.

		Default: "yes"

MKINFO		Can be set to "yes" or "no".  Indicates whether GNU Info
		files, used for the documentation for most of the
		compilation tools, will be built and installed.

		Forced to "no" if NOINFO is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKSHARE=no.

		Default: "yes"

MKIPFILTER	Can be set to "yes" or "no".  Indicates whether the
		ipf(4) programs, headers, and other components will be
		built and installed.

		Default: "yes"

MKISCSI		Can be set to "yes" or "no".  Indicates whether the iSCSI
		library and applications are built and installed.

		Default: "no" on m68000; "yes" on other platforms.

MKKDEBUG	Deprecated, use MKDEBUGKERNEL.

MKKERBEROS	Can be set to "yes" or "no".  Indicates whether the
		Kerberos v5 infrastructure (libraries and support
		programs) will be built and installed.  Caution: the
		default pam(8) configuration requires that Kerberos be
		present even if not used.  Do not install a userland
		without Kerberos without also either updating the
		pam.conf(5) files or disabling PAM via MKPAM.  Otherwise
		all logins will fail.

		Default: "yes"

MKKERBEROS4	Obsolete.

MKKMOD		Can be set to "yes" or "no".  Indicates whether kernel
		modules will be built and installed.

		Default: "no" on or1k; "yes" on other platforms.

MKKYUA		Can be set to "yes" or "no".  Indicates whether Kyua (the
		testing infrastructure used by NetBSD) will be built and
		installed.

		Forced to "no" if MKCXX=no.

		Note: This does not control the installation of the tests
		themselves.  The tests rely on the ATF libraries and
		therefore their build is controlled by the MKATF
		variable.

		Default: "no" until the import of Kyua is done and
		validated.

MKLDAP		Can be set to "yes" or "no".  Indicates whether the
		Lightweight Directory Access Protocol (LDAP)
		infrastructure (libraries and support programs) will be
		built and installed.

		Default: "yes"

MKLIBCSANITIZER
		Can be set to "yes" or "no".  Indicates whether to use
		the sanitizer for libc, using the sanitizer defined by
		USE_LIBCSANITIZER.

		Forced to "no" if NOLIBCSANITIZER is defined, usually in
		the Makefile before any make(1) .include directives.

		Default: "no"

MKLIBCXX	Can be set to "yes" or "no".  Indicates if libc++ will be
		built and installed (usually for clang++(1)).

		Default: "yes" if MKLLVM=yes; "no" otherwise.

MKLIBSTDCXX	Can be set to "yes" or "no".  Indicates if libstdc++ will
		be built and installed (usually for g++(1)).

		Default: "yes"

MKLINKLIB	Can be set to "yes" or "no".  Indicates whether all of
		the shared library infrastructure will be built and
		installed.

		If "no", prevents:
		-   installation of the *.a libraries
		-   installation of the *_pic.a libraries on PIC systems
		-   building of *.a libraries on PIC systems
		-   installation of .so symlinks on ELF systems

		I.e, only install the shared library (and the .so.major
		symlink on ELF).

		Forced to "no" if NOLINKLIB is defined, usually in the
		Makefile before any make(1) .include directives.

		If "no", acts as MKLINT=no MKPICINSTALL=no MKPROFILE=no.

		Default: "yes"

MKLINT		Can be set to "yes" or "no".  Indicates whether lint(1)
		will be run against portions of the NetBSD source code
		during the build, and whether lint libraries will be
		installed into DESTDIR/usr/libdata/lint.

		Forced to "no" if NOLINT is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKLINKLIB=no.

		Default: "no"

MKLLD		Obsolete.

MKLLDB		Obsolete.

MKLLVM		Can be set to "yes" or "no".  Indicates whether clang(1)
		is installed as a host tool and target compiler.

		If "yes", acts as MKLIBCXX=yes.

		Note: Use of clang(1) as the system compiler is
		controlled by HAVE_LLVM.

		Default: "no"

MKLLVMRT	Can be set to "yes" or "no".  Indicates whether to build
		the LLVM PIC libraries necessary for the various Mesa
		backend and the native JIT of the target architecture, if
		supported.  (Radeon R300 and newer, LLVMPIPE for most.)

		Default: If MKX11=yes and HAVE_MESA_VER>=19, "yes" on
		aarch64, amd64, and i386; "no" otherwise.

MKLVM		Can be set to "yes" or "no".  If not "no", build and
		install the logical volume manager.

		Default: "yes"

MKMAKEMANDB	Can be set to "yes" or "no".  Indicates if the whatis
		tools (apropos(1), whatis(1), getNAME(8), makemandb(8),
		and makewhatis(8)), should be built, installed, and used
		to create and install the whatis.db.

		Default: "yes"

MKMAN		Can be set to "yes" or "no".  Indicates whether manual
		pages will be installed.

		Forced to "no" if NOMAN is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKSHARE=no.

		If "no", acts as MKCATPAGES=no MKHTML=no.

		Default: "yes"

MKMANDOC	Can be set to "yes" or "no".  Indicates whether mandoc(1)
		will be built and installed, and used to create and
		install catman and HTML pages.

		If "no", use groff(1) instead of mandoc(1).

		Forced to "no" if NOMANDOC or NOMANDOC.<target> (for a
		given target <target>) is defined, usually in the Makefile
		before any make(1) .include directives.

		Only used if MKMAN=yes.

		Default: "yes"

MKMANZ		Can be set to "yes" or "no".  Indicates whether manual
		pages should be compressed with gzip(1) at installation
		time.

		Only used if MKMAN=yes.

		Default: "no"

MKMCLINKER	Obsolete.

MKMDNS		Can be set to "yes" or "no".  Indicates whether the mDNS
		(Multicast DNS) infrastructure (libraries and support
		programs) will be built and installed.

		Default: "yes"

MKNLS		Can be set to "yes" or "no".  Indicates whether Native
		Language System (NLS) locale zone files will be built and
		installed.

		Forced to "no" if NONLS is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKSHARE=no.

		Default: "yes"

MKNOUVEAUFIRMWARE
		Can be set to "yes" or "no".  Indicates whether to
		install the /libdata/firmware/nouveau directory, which is
		necessary for the nouveau(4) NVIDIA video driver.

		Default: "yes" on aarch64, i386, and x86_64, "no" on
		other platforms.

MKNPF		Can be set to "yes" or "no".  Indicates whether the NPF
		packet filter is to be built and installed.

		Default: "yes"

MKNSD		Can be set to "yes" or "no".  Indicates whether the Name
		Server Daemon (NSD) is to be built and installed.

		Default: "no"

MKOBJ		Can be set to "yes" or "no".  Indicates whether object
		directories will be created when running "make obj".  If
		"no", then all built files will be located inside the
		regular source tree.

		Forced to "no" if NOOBJ is defined, usually in the
		Makefile before any make(1) .include directives.

		If "no", acts as MKOBJDIRS=no.

		Note: Setting MKOBJ to "no" is not recommended and may
		cause problems when updating the tree with cvs(1).

		Default: "yes"

MKOBJDIRS	Can be set to "yes" or "no".  Indicates whether object
		directories will be created automatically (via a "make
		obj" pass) at the start of a build.

		Forced to "no" if MKOBJ=no.

		Default: "no"

MKPAM		Can be set to "yes" or "no".  Indicates whether the
		pam(8) framework (libraries and support files) will be
		built and installed.  The pre-PAM code is not supported
		and may be removed in the future.

		Default: "yes"

MKPCC		Can be set to "yes" or "no".  Indicates whether pcc(1) or
		any related libraries (libpcc, libpccsoftfloat) will be
		built and installed.

		Default: "no"

MKPERFUSE	Obsolete.

MKPF		Can be set to "yes" or "no".  Indicates whether the pf(4)
		programs, headers, and LKM will be built and installed.

		Default: "yes"

MKPIC		Can be set to "yes" or "no".  Indicates whether shared
		objects and libraries will be created and installed.  If
		"no", the entire built system will be statically linked.

		Forced to "no" if NOPIC is defined, usually in the
		Makefile before any make(1) .include directives.

		If "no", acts as MKPICLIB=no.

		Default: "no" on m68000; "yes" on other platforms.

MKPICINSTALL	Can be set to "yes" or "no".  Indicates whether the ar(1)
		format libraries (lib*_pic.a), used to generate shared
		libraries, are installed.

		Forced to "no" if NOPICINSTALL is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKLINKLIB=no.

		Default: "no"

MKPICLIB	Can be set to "yes" or "no".  Indicates whether the ar(1)
		format libraries (lib*_pic.a), used to generate shared
		libraries.

		Forced to "no" if MKPIC=no.

		Default: "no" on vax; "yes" on other platforms.

MKPIE		Indicates whether Position Independent Executables (PIE)
		will be built and installed.

		Forced to "no" if NOPIE is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if COVERITY_TOP_CONFIG is defined.

		This is disabled internally for standalone programs in
		/usr/mdec.

		Default: "yes" on aarch64, arm, i386, m68k, mips, sh3,
		sparc64, and x86_64; "no" on other platforms.

MKPIGZGZIP	Can be set to "yes" or "no".  If "no", the pigz(1)
		utility is not installed as gzip(1).

		Default: "no"

MKPOSTFIX	Can be set to "yes" or "no".  Indicates whether Postfix
		will be built and installed.

		Default: "yes"

MKPROFILE	Can be set to "yes" or "no".  Indicates whether profiled
		libraries (lib*_p.a) will be built and installed.

		Forced to "no" if NOPROFILE is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if MKLINKLIB=no.

		Default: "no" on or1k, riscv32, and riscv64 (due to
		toolchain problems with profiled code); "yes" on other
		platforms.

MKRADEONFIRMWARE
		Can be set to "yes" or "no".  Indicates whether to
		install the /libdata/firmware/radeon directory, which is
		necessary for the radeon(4) AMD RADEON GPU video driver.

		Default: "yes" on aarch64, i386, and x86_64, "no" on
		other platforms.

MKRELRO		Indicates whether to enable support for Relocation Read-
		Only (RELRO).  Supported values:

		partial	 Set the non-PLT GOT to read-only.

		full	 Set the non-PLT GOT to read-only and also force
			 immediate symbol binding, unless NOFULLRELRO is
			 defined and not "no" (usually in the Makefile
			 before any make(1) .include directives).

		no	 Disable RELRO.

		Forced to "no" if NORELRO is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "partial" on aarch64, i386, and x86_64; "no" on
		other platforms.

MKREPRO		Can be set to "yes" or "no".  Indicates whether builds
		are to be reproducible.  If "yes", two builds from the
		same source tree will produce the same build results.

		Used as the default for MKARZERO.

		Default: "no"

MKREPRO_TIMESTAMP
		Unix timestamp.  When MKREPRO is set, the timestamp of
		all files in the sets will be set to this value.

		Default: Unset.

MKRUMP		Can be set to "yes" or "no".  Indicates whether the
		rump(3) headers, libraries, and programs are to be
		installed.

		Forced to "no" if COVERITY_TOP_CONFIG is defined.

		Default: "yes"

MKSANITIZER	Can be set to "yes" or "no".  Indicates whether to use
		the sanitizer to compile userland programs, using the
		sanitizer defined by USE_SANITIZER.

		Forced to "no" if NOSANITIZER is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "no"

MKSHARE		Can be set to "yes" or "no".  Indicates whether files
		destined to reside in DESTDIR/usr/share will be built and
		installed.

		Forced to "no" if NOSHARE is defined, usually in the
		Makefile before any make(1) .include directives.

		If "no", acts as MKCATPAGES=no MKDOC=no MKINFO=no
		MKHTML=no MKMAN=no MKNLS=no.

		Default: "yes"

MKSKEY		Can be set to "yes" or "no".  Indicates whether the S/key
		infrastructure (libraries and support programs) will be
		built and installed.

		Default: "yes"

MKSLJIT		Can be set to "yes" or "no".  Indicates whether to enable
		support for sljit (stack-less platform-independent Just
		in Time (JIT) compiler) private library and tests.

		Default: "yes" on i386, sparc, and x86_64; "no" on other
		platforms.

MKSOFTFLOAT	Can be set to "yes" or "no".  Indicates whether the
		compiler generates output containing library calls for
		floating point and possibly soft-float library support.

		Forced to "yes" on arm without `hf', coldfire, emips,
		or1k, and sh3.

		Default: "yes" on mips64; "no" on other platforms.

MKSTATICLIB	Can be set to "yes" or "no".  Indicates whether the
		normal static libraries (lib*_g.a) will be built and
		installed.

		Forced to "no" if NOSTATICLIB is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "yes"

MKSTATICPIE	Can be set to "yes" or "no".  Indicates whether support
		for static PIE binaries will be built and installed.
		These binaries use a special support in crt0.o for
		resolving relative relocations and require linker
		support.

		Default: "yes" on i386 and x86_64; "no" on other
		platforms.

MKSTRIPIDENT	Can be set to "yes" or "no".  Indicates whether RCS IDs,
		for use with ident(1), should be stripped from program
		binaries and shared libraries.

		Default: "no"

MKSTRIPSYM	Can be set to "yes" or "no".  Indicates whether all local
		symbols should be stripped from shared libraries.  If
		"yes", strip all local symbols from shared libraries; the
		effect is equivalent to the -x option of ld(1).  If "no",
		strip only temporary local symbols; the effect is
		equivalent to the -X option of ld(1).  Keeping non-
		temporary local symbols such as static function names is
		useful on using DTrace for userland libraries and getting
		a backtrace from a rump kernel loading shared libraries.

		Default: "yes"

MKTEGRAFIRMWARE
		Can be set to "yes" or "no".  Indicates whether to
		install the /libdata/firmware/nvidia directory, which is
		necessary for the NVIDIA Tegra XHCI driver.

		Default: "yes" on evbarm; "no" on other platforms.

MKTOOLSDEBUG	Deprecated, use MKDEBUGTOOLS.

MKTPM		Can be set to "yes" or "no".  Indicates whether to
		install the Trusted Platform Module (TPM) infrastructure.

		Default: "no"

MKUNBOUND	Can be set to "yes" or "no".  Indicates whether the
		unbound(8) DNS resolver will be built and installed.

		Default: "yes"

MKUNPRIVED	Can be set to "yes" or "no".  Indicates whether an
		unprivileged install will occur.  The user, group,
		permissions, and file flags, will not be set on the
		installed items; instead the information will be appended
		to a file called METALOG in DESTDIR.  The contents of
		METALOG is used during the generation of the distribution
		tar files to ensure that the appropriate file ownership
		is stored.  This allows a non-root `make install'.

		Default: "no"

MKUPDATE	Can be set to "yes" or "no".  Indicates whether all
		install operations intended to write to DESTDIR will
		compare file timestamps before installing, and skip the
		install phase if the destination files are up-to-date.

		Default: "no"

MKX11		Can be set to "yes" or "no".  Indicates whether X11 will
		be built and installed from X11SRCDIR, and whether the X
		sets will be created.

		Note: If "yes", requires MKINET6=yes.

		Default: "no"

MKX11FONTS	Can be set to "yes" or "no".  If "no", do not build and
		install the X fonts.  The xfont set is still created but
		will be empty.

		Only used if MKX11=yes.

		Default: "yes"

MKX11MOTIF	Can be set to "yes" or "no".  If "yes", build the native
		Xorg libGLw with Motif stubs.  Requires that Motif can be
		found via X11MOTIFPATH.

		Default: "no"

MKXORG_SERVER	Can be set to "yes" or "no".  Indicates whether the
		Xorg(7) X server and drivers will be built and installed.

		Default: "yes" on alpha, amd64, amiga, bebox, cats,
		dreamcast, ews4800mips, evbarm, evbmips, evbppc, hp300,
		hpcarm, hpcmips, hpcsh, hppa, i386, ibmnws, iyonix,
		luna68k, mac68k, macppc, netwinder, newsmips, pmax, prep,
		ofppc, sgimips, shark, sparc, sparc64, vax, and zaurus;
		"no" on other platforms.

MKYP		Can be set to "yes" or "no".  Indicates whether the YP
		(NIS) infrastructure (libraries and support programs)
		will be built and installed.

		Default: "yes"

MKZFS		Can be set to "yes" or "no".  Indicates whether the ZFS
		kernel module and the utilities and libraries used to
		manage the ZFS system are to be built and installed.

		Note: ZFS requires 64-bit atomic operations .

		Default: "yes" on aarch64, amd64, and sparc64; "no" on
		other platforms.

NETBSD_OFFICIAL_RELEASE
		Can be set to "yes" or "no".  Indicates whether the build
		creates an official NetBSD release which is going to be
		available from ftp.NetBSD.org and/or cdn.NetBSD.org
		locations.  This variable modifies a few default paths in
		the installer and also creates different links in the
		install documentation.  The auto-build cluster uses this
		variable to distinguish `daily' builds from real
		releases.

		Default: Unset.  ("no").

USE_FORT	Can be set to "yes" or "no".  Indicates whether the so-
		called "FORTIFY_SOURCE" security(7) extensions are
		enabled; see ssp(3) for details.  This imposes some
		performance penalty.

		Forced to "no" if NOFORT is defined, usually in the
		Makefile before any make(1) .include directives.

		Default: "no"

USE_HESIOD	Can be set to "yes" or "no".  Indicates whether Hesiod
		support is enabled in the various applications that
		support it.

		Forced to "no" if MKHESIOD=no.

		Default: "yes"

USE_INET6	Can be set to "yes" or "no".  Indicates whether INET6
		(IPv6) support is enabled in the various applications
		that support it.

		Forced to "no" if MKINET6=no.

		Default: "yes"

USE_JEMALLOC	Can be set to "yes" or "no".  Indicates whether the
		jemalloc allocator (which is designed for improved
		performance with threaded applications) is used instead
		of the phkmalloc allocator (that was the default until
		NetBSD 5.0).

		Default: "yes"

USE_KERBEROS	Can be set to "yes" or "no".  Indicates whether Kerberos
		v5 support is enabled in the various applications that
		support it.

		Forced to "no" if MKKERBEROS=no.

		Default: "yes"

USE_LDAP	Can be set to "yes" or "no".  Indicates whether LDAP
		support is enabled in the various applications that
		support it.

		Forced to "no" if MKLDAP=no.

		Default: "yes"

USE_LIBCSANITIZER
		Selects the sanitizer in libc to compile userland
		programs and libraries.  Supported values:

		undefined  Enables the micro-UBSan in the user mode
			   (uUBSan) undefined behaviour sanitizer.  The
			   code is shared with the kernel mode variation
			   (kUBSan).  The runtime runtime differs from
			   the UBSan available in MKSANITIZER.  The
			   runtime is stripped down from C++ features,
			   and is invoked with -fsanitize=no-vptr as that
			   sanitizer is not supported.  The runtime
			   configuration is restricted to the LIBC_UBSAN
			   environment variable, that is designed to be
			   safe for hardening.

		The value of USE_LIBCSANITIZER is passed to the C and C++
		compilers as the argument to -fsanitize=.  Additional
		sanitizer arguments can be passed through
		LIBCSANITIZERFLAGS.

		Disabled if MKLIBCSANITIZER=no.

		Default: "undefined".

USE_PAM		Can be set to "yes" or "no".  Indicates whether pam(8)
		support is enabled in the various applications that
		support it.

		Forced to "no" if MKPAM=no.

		Default: "yes"

USE_PIGZGZIP	Can be set to "yes" or "no".  Indicates whether pigz(1)
		is used instead of gzip(1) for multi-threaded gzip
		compression of the distribution tar sets.

		Default: "no"

USE_SKEY	Can be set to "yes" or "no".  Indicates whether S/key
		support is enabled in the various applications that
		support it.

		Forced to "no" if MKSKEY=no.

		Note: This is mutually exclusive to USE_PAM!=no.

		Default: "no"

USE_SSP		Can be set to "yes" or "no".  Indicates whether GCC
		stack-smashing protection (SSP) support, which detects
		stack overflows and aborts the program, is enabled.  This
		imposes some performance penalty (approximately 5%).

		This is disabled internally for standalone programs in
		/usr/mdec.

		Forced to "no" if NOSSP is defined, usually in the
		Makefile before any make(1) .include directives.

		Forced to "no" if COVERITY_TOP_CONFIG is defined.

		Default: "no" on alpha, hppa, ia64, and mips; "yes" on
		other platforms if USE_FORT=yes; "no" otherwise.

USE_XZ_SETS	Can be set to "yes" or "no".  Indicates whether the
		distribution tar files are to be compressed with xz(1)
		instead of gzip(1) or pigz(1).

		Forced to "no" if USE_PIGZGZIP=yes.

		Default: "yes" on aarch64, amd64, and sparc64, "no" on
		other platforms.

USE_YP		Can be set to "yes" or "no".  Indicates whether YP (NIS)
		support is enabled in the various applications that
		support it.

		Forced to "no" if MKYP=no.

		Default: "yes"

X11MOTIFPATH	Path of the Motif installation to use if MKX11MOTIF=yes.

		Default: "/usr/pkg"

COPTS.lib<lib>
OBJCOPTS.lib<lib>
LDADD.lib<lib>
CPPFLAGS.lib<lib>
CXXFLAGS.lib<lib>
COPTS.<prog>
OBJCOPTS.<prog>
LDADD.<prog>
CPPFLAGS.<prog>
CXXFLAGS.<prog> These provide a way to specify additions to the associated
		variables in a way that applies only to a particular library
		or program.  <lib> corresponds to the LIB variable set in
		the library's makefile.  <prog> corresponds to either PROG
		or PROG_CXX (if set).  For example, if COPTS.libcrypto is
		set to "-g", "-g" will be added to COPTS only when compiling
		the crypto library.

The active compiler is selected using the following variables:
AVAILABLE_COMPILER
		List of available compiler suites.  Processed in order
		for selecting the active compiler for each frontend.
HAVE_PCC	If defined, PCC is present and enabled.
HAVE_LLVM	If defined, LLVM/Clang is present and enabled.
UNSUPPORTED_COMPILER.<comp>
		If defined, the support for compiler <comp> is disabled.

For the frontends (CC, CPP, CXX, FC and OBJC) the following variables exist:
ACTIVE_CC	Active compile suite for the CC frontend.
SUPPORTED_CC	Compile suite with support for the CC frontend.
TOOL_CC.<comp>	Path to the CC frontend for compiler <comp>.


=-=-=-=-=   Variables for a Makefile   =-=-=-=-=

If the following varialbes are defined in the Makefile before
any make(1) .include directives, they force the specific behavior.

NOCOMPAT	Force MKCOMPAT=no.
NOCTF		Force MKCTF=no.
NODEBUG		Force MKDEBUG=no.
NODEBUGLIB	Force MKDEBUGLIB=no.
NODOC		Force MKDOC=no.
NOFORT		Force USE_FORT=no.
NOHTML		Force MKHTML=no.
NOINFO		Force MKINFO=no.
NOLIBCSANITIZER Force MKLIBCSANITIZER=no (and USE_LIBCSANITIZER=no)
NOLINKLIB	Force MKLINKLIB=no.
NOLINT		Force MKLINT=no.
NOMAN		Force MKMAN=no.
NOMANDOC	Force MKMANDOC=no.
NONLS		Force MKNLS=no.
NOOBJ		Force MKOBJ=no.
NOPIC		Force MKPIC=no.
NOPICINSTALL	Force MKPICINSTALL=no.
NOPIE		Force MKPIE=no.
NOPROFILE	Force MKPROFILE=no.
NORELRO		Force MKREPRO=no.
NOSANITIZER	Force MKSANITIZER=no (and USE_SANITIZER=no)
NOSHARE		Force MKSHARE=no.
NOSSP		Force USE_SSP=no.
NOSTATICLIB	Force MKSTATICLIB=no.

Special variations:

NOFULLRELRO!=no Force MKRELRO=no if MKRELRO=full

TODO: NOFULLRELRO should just be a defined test for consistency.


=-=-=-=-=   sys.mk   =-=-=-=-=

The include file <sys.mk> has the default rules for all makes, in the BSD
environment or otherwise.  You probably don't want to touch this file.

=-=-=-=-=   bsd.own.mk   =-=-=-=-=

The include file <bsd.own.mk> contains source tree configuration parameters,
such as the owners, groups, etc. for both manual pages and binaries, and
a few global "feature configuration" parameters.

It has no targets.

To get system-specific configuration parameters, <bsd.own.mk> will try to
include the file specified by the "MAKECONF" variable.  If MAKECONF is not
set, or no such file exists, the system make configuration file, /etc/mk.conf
is included.  These files may define any of the variables described below.

<bsd.own.mk> sets the following variables, if they are not already defined
(defaults are in brackets):

NETBSDSRCDIR	Top of the NetBSD source tree.
		If _SRC_TOP_ != "", that will be used as the default,
		otherwise BSDSRCDIR will be used as the default.
		Various makefiles within the NetBSD source tree will
		use this to reference the top level of the source tree.

_SRC_TOP_	Top of the system source tree, as determined by <bsd.own.mk>
		based on the presence of tools/ and build.sh.  This variable
		is "internal" to <bsd.own.mk>, although its value is only
		determined once and then propagated to all sub-makes.

_NETBSD_VERSION_DEPENDS
		A list of files which contain information about
		the version of the NetBSD being built.  This is
		defined only if the current directory appears
		to be inside a NetBSD source tree.  The list of
		files includes ${NETBSDSRCDIR}/sys/sys/param.h
		(which contains the kernel version number),
		${NETBSDSRCDIR}/sys/conf/newvers.sh and
		${NETBSDSRCDIR}/sys/conf/osrelease.sh (which
		interpret the information in sys/sys/param.h), and
		${_SRC_TOP_OBJ_}/params (which is an optional file,
		created by "make build" in ${_SRC_TOP_}/Makefile,
		containing all the variables that may influence the
		build).

		Targets that depend on the NetBSD version, or on
		variables defined at build time, can declare a
		dependency on ${_NETBSD_VERSION_DEPENDS}, like this:

			version.c: ${_NETBSD_VERSION_DEPENDS}
				commands to create version.c

BSDSRCDIR	The real path to the system sources, so that 'make obj'
		will work correctly.  [/usr/src]

BSDOBJDIR	The real path to the system 'obj' tree, so that 'make obj'
		will work correctly.  [/usr/obj]

BINGRP		Binary group.  [wheel]

BINOWN		Binary owner.  [root]

BINMODE		Binary mode.  [555]

NONBINMODE	Mode for non-executable files.  [444]

MANDIR		Base path for manual installation.  [/usr/share/man/cat]

MANGRP		Manual group.  [wheel]

MANOWN		Manual owner.  [root]

MANMODE		Manual mode.  [${NONBINMODE}]

MANINSTALL	Manual installation type.  Space separated list:
			catinstall, htmlinstall, maninstall
		Default value derived from MKCATPAGES and MKHTML.

LDSTATIC	Control program linking; if set blank, link everything
		dynamically.  If set to "-static", link everything statically.
		If not set, programs link according to their makefile.

LIBDIR		Base path for library installation.  [/usr/lib]

LINTLIBDIR	Base path for lint(1) library installation.  [/usr/libdata/lint]

LIBGRP		Library group.  [${BINGRP}]

LIBOWN		Library owner.  [${BINOWN}]

LIBMODE		Library mode.  [${NONBINMODE}]

DOCDIR		Base path for system documentation (e.g. PSD, USD, etc.)
		installation.  [/usr/share/doc]

DOCGRP		Documentation group.  [wheel]

DOCOWN		Documentation owner.  [root]

DOCMODE		Documentation mode.  [${NONBINMODE}]

GZIP_N_FLAG	Flags to pass to TOOL_GZIP to prevent it from inserting
		file names or timestamps in the compressed output.
		[-n, or -nT when TOOL_GZIP is really TOOL_PIGZ]

NLSDIR		Base path for Native Language Support files installation.
		[/usr/share/nls]

NLSGRP		Native Language Support files group.  [wheel]

NLSOWN		Native Language Support files owner.  [root]

NLSMODE		Native Language Support files mode.  [${NONBINMODE}]

X11SRCDIR	The path to the xsrc tree.  [${NETBSDSRCDIR}/../xsrc,
		if that exists; otherwise /usr/xsrc]

X11SRCDIR.local The path to the local X11 src tree.  [${X11SRCDIR}/local]

X11SRCDIR.lib<package>
X11SRCDIR.<package>
		The path to the xorg src tree for the specified package>.
		[${X11SRCDIR}/external/mit/xorg/<package>/dist]

X11ROOTDIR	Root directory of the X11 installation.  [/usr/X11R7]

X11BINDIR	X11 bin directory.  [${X11ROOTDIR}/bin]

X11FONTDIR	X11 font directory.  [${X11ROOTDIR}/lib/X11/fonts]

X11INCDIR	X11 include directory.  [${X11ROOTDIR}/include]

X11LIBDIR	X11 lib/x11 (config) directory.  [${X11ROOTDIR}/lib/X11]

X11MANDIR	X11 manual directory.  [${X11ROOTDIR}/man]

X11USRLIBDIR	X11 library directory.  [${X11ROOTDIR}/lib]

STRIPFLAG	The flag passed to the install program to cause the binary
		to be stripped.  This is to be used when building your
		own install script so that the entire system can be made
		stripped/not-stripped using a single knob.  []

COPY		The flag passed to the install program to cause the binary
		to be copied rather than moved.  This is to be used when
		building our own install script so that the entire system
		can either be installed with copies, or with moves using
		a single knob.  [-c]

MAKEDIRTARGETENV
		Environment variables passed to the child make process
		invoked by MAKEDIRTARGET.

MAKEDIRTARGET dir target [params]
		Runs "cd $${dir} && ${MAKE} [params] $${target}",
		displaying a "pretty" message whilst doing so.

RELEASEMACHINEDIR
		Subdirectory used below RELEASEDIR when building
		a release.  [${MACHINE},
		or ${MACHINE}-${MACHINE_ARCH} for evb{arm,mips,sh3}*]

RELEASEMACHINE	Subdirectory or path component used for the following
		paths:
			distrib/${RELEASEMACHINE}
			distrib/notes/${RELEASEMACHINE}
			etc/etc.${RELEASEMACHINE}
		Used when building a release.  [${MACHINE}]

Additionally, the following variables may be set by <bsd.own.mk> or in a
make configuration file to modify the behavior of the system build
process (default values are in brackets along with comments, if set by
<bsd.own.mk>):

USETOOLS	Indicates whether the tools specified by ${TOOLDIR} should
		be used as part of a build in progress.
		Supported values:

		yes	Use the tools from TOOLDIR.
			Must be set to this if cross-compiling.

		no	Do not use the tools from TOOLDIR, but refuse to
			build native compilation tool components that are
			version-specific for that tool.

		never	Do not use the tools from TOOLDIR, even when
			building native tool components.  This is similar to
			the traditional NetBSD build method, but does not
			verify that the compilation tools in use are
			up-to-date enough in order to build the tree
			successfully.  This may cause build or runtime
			problems when building the whole NetBSD source tree.

		Default: "yes" if building all or part of a whole NetBSD
		source tree (detected automatically); "no" otherwise
		(to preserve traditional semantics of the <bsd.*.mk>
		make(1) include files).

OBJECT_FMT	Object file format.  [set to "ELF" on architectures that
		use ELF -- currently all architectures].

KERNEL_DIR	Install the kernel as /netbsd/kernel and the modules
		in /netbsd/modules, defaults to "no".

TOOLCHAIN_MISSING
		If not "no", this indicates that the platform being built
		does not have a working in-tree toolchain.  If the
		${MACHINE_ARCH} in question falls into this category,
		TOOLCHAIN_MISSING is conditionally assigned the value "yes".
		Otherwise, the variable is unconditionally assigned the
		value "no".
		If not "no", ${MKBINUTILS}, ${MKGCC}, and ${MKGDB} are
		unconditionally assigned the value "no".

EXTERNAL_TOOLCHAIN
		This variable is not directly set by <bsd.own.mk>, but
		including <bsd.own.mk> is the canonical way to gain
		access to this variable.  The variable should be defined
		either in the user's environment or in the user's mk.conf
		file.  If defined, this variable indicates the root of
		an external toolchain which will be used to build the
		tree.  For example, if a platform is a ${TOOLCHAIN_MISSING}
		platform, EXTERNAL_TOOLCHAIN can be used to re-enable the
		cross-compile framework.

		If EXTERNAL_TOOLCHAIN is defined, ${MKGCC} is unconditionally
		assigned the value "no", since the external version of the
		compiler may not be able to build the library components of
		the in-tree compiler.

		This variable should be used in conjunction with an appropriate
		HAVE_GCC or HAVE_LLVM setting to control the compiler flags.

		NOTE: This variable is not yet used in as many places as
		it should be.  Expect the exact semantics of this variable
		to change in the short term as parts of the cross-compile
		framework continue to be cleaned up.

The following variables are defined to commands to perform the
appropriate operation, with the default in [brackets].  Note that
the defaults change if USETOOLS == "yes":

TOOL_AMIGAAOUT2BB	aout to Amiga bootblock converter.  [amiga-aout2bb]

TOOL_AMIGAELF2BB	ELF to Amiga bootblock converter.  [amiga-elf2bb]

TOOL_AMIGATXLT		Amiga assembly language format translator.  [amiga-txlt]

TOOL_ARMELF2AOUT	ELF to a.out executable converter [arm-elf2aout}

TOOL_ASN1_COMPILE	ASN1 compiler.  [asn1_compile]

TOOL_AWK		Pattern-directed scanning/processing language.  [awk]

TOOL_CAP_MKDB		Create capability database.  [cap_mkdb]

TOOL_CAT		Concatenate and print files.  [cat]

TOOL_CKSUM		Display file checksums.  [cksum]

TOOL_COMPILE_ET		Error table compiler.  [compile_et]

TOOL_CONFIG		Build kernel compilation directories.  [config]

TOOL_CRUNCHGEN		Generate crunched binary build environment.  [crunchgen]

TOOL_CTAGS		Create a tags file.  [ctags]

TOOL_DB			Manipulate db(3) databases.  [db]

TOOL_DISKLABEL		Read and write disk pack label.  [disklabel]

TOOL_EQN		Format equations for groff.  [eqn]

TOOL_FDISK		MS-DOS partition maintenance program.  [fdisk]

TOOL_FGEN		IEEE 1275 Open Firmware FCode Tokenizer.  [fgen]

TOOL_GENASSYM		Generate constants for assembly files.  [genassym]

TOOL_GENCAT		Generate NLS message catalogs.  [gencat]

TOOL_GMAKE		GNU make utility.  [gmake]

TOOL_GREP		Print lines matching a pattern.  [grep]

TOOL_GROFF		Front end for groff document formatting system.  [groff]

TOOL_GZIP		Compression/decompression tool.  [gzip]

TOOL_GZIP_N		Same as TOOL_GZIP, plus a command line option to
			prevent it from inserting file names or timestamps
			into the compressed output.
			[${TOOL_GZIP} ${GZIP_N_FLAG}]

TOOL_HEXDUMP		Ascii, decimal, hexadecimal, octal dump.  [hexdump]

TOOL_HP300MKBOOT	Make bootable image for hp300.  [hp300-mkboot]

TOOL_HPPAMKBOOT		Make bootable image for hppa.  [hppa-mkboot]

TOOL_INDXBIB		Make bibliographic database's inverted index.  [indxbib]

TOOL_INSTALLBOOT	Install disk bootstrap software.  [installboot]

TOOL_INSTALL_INFO	Update info/dir entries.  [install-info]

TOOL_JOIN		Relational database operator.  [join]

TOOL_M4			M4 macro language processor.  [m4]

TOOL_M68KELF2AOUT	ELF to a.out executable converter [m68k-elf2aout}

TOOL_MACPPCFIXCOFF	Fix up xcoff headers for macppc.  [macppc-fixcoff]

TOOL_MAKEFS		Create file system image from directory tree.  [makefs]

TOOL_MAKEINFO		Translate Texinfo documents.  [makeinfo]

TOOL_MAKEWHATIS		Create a whatis.db database.  [makewhatis]

TOOL_MDSETIMAGE		Set kernel RAM disk image.  [mdsetimage]

TOOL_MENUC		Menu compiler.  [menuc]

TOOL_MIPSELF2ECOFF	Convert ELF-format executable to ECOFF for mips.
			[mips-elf2ecoff]

TOOL_MKCSMAPPER		Make charset mapping table.  [mkcsmapper]

TOOL_MKESDB		Make encoding scheme database.  [mkesdb]

TOOL_MKLOCALE		Make LC_CTYPE locale files.  [mklocale]

TOOL_MKMAGIC		Create database for file(1).  [file]

TOOL_MKNOD		Make device special file.  [mknod]

TOOL_MKTEMP		Make (unique) temporary file name.  [mktemp]

TOOL_MSGC		Simple message list compiler.  [msgc]

TOOL_MTREE		Map a directory hierarchy.  [mtree]

TOOL_NCDCS		Turn ELF kernel into a NCD firmware image. [ncdcs]

TOOL_PAX		Manipulate file archives and copy directories.  [pax]

TOOL_PIC		Compile pictures for groff.  [pic]

TOOL_PIGZ		Parallel compressor.  [pigz]

TOOL_POWERPCMKBOOTIMAGE Make bootable image for powerpc.  [powerpc-mkbootimage]

TOOL_PWD_MKDB		Generate the password databases.  [pwd_mkdb]

TOOL_REFER		Preprocess bibliographic references for groff.  [refer]

TOOL_ROFF_ASCII		Generate ASCII groff output.  [nroff]

TOOL_ROFF_DVI		Generate DVI groff output.  [${TOOL_GROFF} -Tdvi]

TOOL_ROFF_HTML		Generate HTML groff output.
			[${TOOL_GROFF} -Tlatin1 -mdoc2html]

TOOL_ROFF_PS		Generate PS groff output.  [${TOOL_GROFF} -Tps]

TOOL_ROFF_RAW		Generate "raw" groff output.  [${TOOL_GROFF} -Z]

TOOL_RPCGEN		Remote Procedure Call (RPC) protocol compiler.  [rpcgen]

TOOL_SED		Stream editor.  [sed]

TOOL_SOELIM		Eliminate .so's from groff input.  [soelim]

TOOL_SPARKCRC		Generate a crc suitable for use in a sparkive file.
			[sparkcrc]

TOOL_STAT		Display file status.  [stat]

TOOL_STRFILE		Create a random access file for storing strings.
			[strfile]

TOOL_SUNLABEL		Read or modify a SunOS disk label.  [sunlabel]

TOOL_TBL		Format tables for groff.  [tbl]

TOOL_UUDECODE		Uudecode a binary file.  [uudecode]

TOOL_VGRIND		Grind nice listings of programs.  [vgrind -f]

TOOL_ZIC		Time zone compiler.  [zic]

For each possible value of MACHINE_CPU, MACHINES.${MACHINE_CPU} contain a
list of what ports can be built for it.  This keeps those definitions in
centralized place.

<bsd.own.mk> is generally useful when building your own Makefiles so that
they use the same default owners etc. as the rest of the tree.


=-=-=-=-=   bsd.clean.mk   =-=-=-=-=

The include file <bsd.clean.mk> defines the clean and cleandir
targets.  It uses the following variables:

CLEANFILES	Files to remove for both the clean and cleandir targets.

CLEANDIRFILES	Files to remove for the cleandir target, but not for
		the clean target.

MKCLEANSRC	Controls whether or not the clean and cleandir targets
		will delete files from both the object directory,
		${.OBJDIR}, and the source directory, ${.CURDIR}.

		If MKCLEANSRC is set to "no", then the file names in
		CLEANFILES or CLEANDIRFILES are interpreted relative
		to the object directory, ${.OBJDIR}.  This is the
		traditional behaviour.

		If MKCLEANSRC is set to "yes", then the file deletion
		is performed relative to both the object directory,
		${.OBJDIR}, and the source directory, ${.CURDIR}.  (This
		has no effect if ${.OBJDIR} is the same as ${.CURDIR}.)
		Deleting files from ${.CURDIR} is intended to remove
		stray output files that had been left in the source
		directory by an earlier build that did not use object
		directories.

		The default is MKCLEANSRC=yes.  If you always build with
		separate object directories, and you are sure that there
		are no stray files in the source directories, then you
		may set MKCLEANSRC=no to save some time.

MKCLEANVERIFY	Controls whether or not the clean and cleandir targets
		will verify that files have been deleted.

		If MKCLEANVERIFY is set to "no", then the files will
		be deleted using a "rm -f" command, and its success or
		failure will be ignored.

		If MKCLEANVERIFY is set to "yes", then the success of
		the "rm -f" command will be verified using an "ls"
		command.

		The default is MKCLEANVERIFY=yes.  If you are sure that
		there will be no problems caused by file permissions,
		read-only file systems, or the like, then you may set
		MKCLEANVERIFY=no to save some time.

To use the clean and cleandir targets defined in <bsd.clean.mk>, other
Makefiles or bsd.*.mk files should append file names to the CLEANFILES
or CLEANDIRFILES variables.  For example:

	    CLEANFILES+= a.out
	    CLEANDIRFILES+= .depend

	    .include <bsd.clean.mk>

The files listed in CLEANFILES and CLEANDIRFILES must not be
directories, because the potential risk from running "rm -rf" commands
in bsd.clean.mk is considered too great.  If you want to recursively
delete a directory as part of "make clean" or "make cleandir" then you
need to provide your own target.

=-=-=-=-=   bsd.dep.mk   =-=-=-=-=

The include file <bsd.dep.mk> contains the default targets for building
.depend files.  It creates .d files from entries in SRCS and DPSRCS
that are C, C++, or Objective C source files, and builds .depend from the
.d files.  All other files in SRCS and all of DPSRCS will be used as
dependencies for the .d files.  In order for this to function correctly,
it should be .included after all other .mk files and directives that may
modify SRCS or DPSRCS.  It uses the following variables:

SRCS		List of source files to build the program.

DPSRCS		List of source files which are needed for generating
		dependencies, but are not needed in ${SRCS}.

NODPSRCS	TODO

=-=-=-=-=   bsd.files.mk   =-=-=-=-=

The include file <bsd.files.mk> handles the FILES variables and is included
from <bsd.lib.mk> and <bsd.prog.mk>, and uses the following variables:

FILES		The list of files to install.

CONFIGFILES	Similar semantics to FILES, except that the files
		are installed by the `configinstall' target,
		not the `install' target.
		The FILES* variables documented below also apply.

FILESOWN	File owner.  [${BINOWN}]

FILESGRP	File group.  [${BINGRP}]

FILESMODE	File mode.  [${NONBINMODE}]

FILESDIR	The location to install the files.

FILESNAME	Optional name to install each file as.

FILESOWN_<fn>	File owner of the specific file <fn>.

FILESGRP_<fn>	File group of the specific file <fn>.

FILESMODE_<fn>	File mode of the specific file <fn>.

FILESDIR_<fn>	The location to install the specific file <fn>.

FILESNAME_<fn>	Optional name to install <fn> as.

FILESBUILD	If this variable is defined, then its value will be
		used as the default for all FILESBUILD_<fn> variables.
		Otherwise, the default will be "no".

FILESBUILD_<fn> A value different from "no" will add the file to the list of
		targets to be built by `realall'.  Users of that variable
		should provide a target to build the file.


BUILDSYMLINKS	List of two word items:
			lnsrc lntgt
		For each lnsrc item, create a symlink named lntgt.
		The lntgt symlinks are removed by the cleandir target.

UUDECODE_FILES	List of files which are stored as <file>.uue in the source
		tree. Each one will be decoded with ${TOOL_UUDECODE}.
		The source files have a `.uue' suffix, the generated files do
		not.

UUDECODE_FILES_RENAME_<fn>
		Rename the output from the decode to the provided name.

		*NOTE: These files are simply decoded, with no install or other
		       rule applying implicitly except being added to the clean
		       target.

=-=-=-=-=   bsd.gcc.mk   =-=-=-=-=

The include file <bsd.gcc.mk> computes various parameters related to GCC
support libraries.  It defines no targets.  <bsd.own.mk> MUST be included
before <bsd.gcc.mk>.

The primary users of <bsd.gcc.mk> are <bsd.prog.mk> and <bsd.lib.mk>, each
of which need to know where to find certain GCC support libraries.

The behavior of <bsd.gcc.mk> is influenced by the EXTERNAL_TOOLCHAIN variable,
which is generally set by the user.  If EXTERNAL_TOOLCHAIN it set, then
the compiler is asked where to find the support libraries, otherwise the
support libraries are found in ${DESTDIR}/usr/lib.

<bsd.gcc.mk> sets the following variables:

_GCC_CRTBEGIN	The full path name to crtbegin.o.

_GCC_CRTBEGINS	The full path name to crtbeginS.o.

_GCC_CRTEND	The full path name to crtend.o.

_GCC_CRTENDS	The full path name to crtendS.o.

_GCC_LIBGCCDIR	The directory where libgcc.a is located.


=-=-=-=-=   bsd.inc.mk   =-=-=-=-=

The include file <bsd.inc.mk> defines the includes target and uses the
variables:

INCS		The list of include files.

INCSDIR		The location to install the include files.

INCSNAME	Target name of the include file, if only one; same as
		FILESNAME, but for include files.

INCSYMLINKS	Similar to SYMLINKS in <bsd.links.mk>, except that these
		are installed in the 'includes' target and not the
		(much later) 'install' target.

INCSNAME_<file> The name file <file> should be installed as, if not <file>,
		same as FILESNAME_<file>, but for include files.


=-=-=-=-=   bsd.info.mk   =-=-=-=-=

The include file <bsd.info.mk> is used to generate and install GNU Info
documentation from respective Texinfo source files.  It defines three
implicit targets (.txi.info, .texi.info, and .texinfo.info), and uses the
following variables:

TEXINFO		List of Texinfo source files.  Info documentation will
		consist of single files with the extension replaced by
		.info.

INFOFLAGS	Flags to pass to makeinfo.  []


=-=-=-=-=   bsd.kernobj.mk   =-=-=-=-=

The include file <bsd.kernobj.mk> defines variables related to the
location of kernel sources and object directories.

KERNSRCDIR	Is the location of the top of the kernel src.
		[${_SRC_TOP_}/sys]

KERNARCHDIR	Is the location of the machine dependent kernel sources.
		[arch/${MACHINE}]

KERNCONFDIR	Is where the configuration files for kernels are found.
		[${KERNSRCDIR}/${KERNARCHDIR}/conf]

KERNOBJDIR	Is the kernel build directory.  The kernel GENERIC for
		instance will be compiled in ${KERNOBJDIR}/GENERIC.
		The default value is
		${MAKEOBJDIRPREFIX}${KERNSRCDIR}/${KERNARCHDIR}/compile
		if it exists or the target 'obj' is being made.
		Otherwise the default is
		${KERNSRCDIR}/${KERNARCHDIR}/compile.

It is important that Makefiles (such as those under src/distrib) that
wish to find compiled kernels use <bsd.kernobj.mk> and ${KERNOBJDIR}
rather than make assumptions about the location of the compiled kernel.


=-=-=-=-=   bsd.kinc.mk   =-=-=-=-=

The include file <bsd.kinc.mk> defines the many targets (includes,
subdirectories, etc.), and is used by kernel makefiles to handle
include file installation.  It is intended to be included alone, by
kernel Makefiles.  It uses similar variables to <bsd.inc.mk>.
Please see <bsd.kinc.mk> for more details, and keep the documentation
in that file up to date.

=-=-=-=-=   bsd.syscall.mk =-=-=-=-=

The include file <bsd.syscall.mk> contains the logic to create syscall
files for various emulations. It includes <bsd.kinc.mk> to handle the
rest of the targets.

=-=-=-=-=   bsd.lib.mk   =-=-=-=-=

The include file <bsd.lib.mk> has support for building libraries.  It has
the same eight targets as <bsd.prog.mk>: all, clean, cleandir, depend,
includes, install, lint, and tags.  Additionally, it has a checkver target
which checks for installed shared object libraries whose version is greater
that the version of the source. It has a limited number of suffixes,
consistent with the current needs of the BSD tree.  <bsd.lib.mk> includes
<bsd.shlib.mk> to get shared library parameters.

It sets/uses the following variables:

LIB		The name of the library to build.

LIBDIR		Target directory for libraries.

MKARZERO	Normally, ar(1) sets the timestamps, uid, gid and
		permissions in files inside its archives to those of
		the file it was fed. This leads to non-reproducible
		builds. If MKARZERO is set to "yes" (default is the
		same as MKREPRO, or "no" if MKREPRO is not defined),
		then the "D" flag is passed to ar, causing the
		timestamp, uid and gid to be zeroed and the file
		permissions to be set to 644. This allows .a files
		from different builds to be bit identical.

SHLIBINSTALLDIR Target directory for shared libraries if ${USE_SHLIBDIR}
		is not "no".

SHLIB_MAJOR
SHLIB_MINOR
SHLIB_TEENY	Major, minor, and teeny version numbers of shared library

USE_SHLIBDIR	If not "no", use ${SHLIBINSTALLDIR} instead of ${LIBDIR}
		as the path to install shared libraries to.
		USE_SHLIBDIR must be defined before <bsd.own.mk> is included.
		Default: no

LIBISMODULE	If not "no", install as ${LIB}.so (without the "lib" prefix),
		and act as "MKDEBUGLIB=no MKPICINSTALL=no MKPROFILE=no
		MKSTATICLIB=no". Also do not install the lint library.
		Default: no

LIBISPRIVATE	If not "no", act as "MKDEBUGLIB=no MKPIC=no MKPROFILE=no",
		and don't install the (.a) library or the lint library.
		This is useful for "build only" helper libraries.
		If set to "pic", then a _pic.a library is also produced,
		so that it can be incorporated into other shared objects.
		Default: no

LIBISCXX	If not "no", Use ${CXX} instead of ${CC} to link
		shared libraries.
		This is useful for C++ libraries.
		Default: no

LINTLIBDIR	Target directory for lint libraries.

LIBGRP		Library group.

LIBOWN		Library owner.

LIBMODE		Library mode.

LDADD		Additional loader objects.

MAN		The manual pages to be installed (use a .1 - .9 suffix).

NOCHECKVER_<library>
NOCHECKVER	If set, disables checking for installed shared object
		libraries with versions greater than the source.  A
		particular library name, without the "lib" prefix, may
		be appended to the variable name to disable the check for
		only that library.

SRCS		List of source files to build the library.  Suffix types
		.s, .c, and .f are supported.  Note, .s files are preferred
		to .c files of the same name.  (This is not the default for
		versions of make.)

LIBDPLIBS/
PROGDPLIBS	A list of the tuples:
			libname	 path-to-srcdir-of-libname

		Instead of depending on installed versions of the libraries,
		one can depend on their built version in the source directory.
		This is useful for finding private libraries (LIBISPRIVATE).

		For each tuple;
		     *	LIBDO.libname contains the .OBJDIR of the library
			`libname', and if it is not set it is determined
			from the srcdir and added to MAKEOVERRIDES (the
			latter is to allow for build time optimization).
		     *	LDADD gets  -L${LIBDO.libname} -llibname    added.
		     *	DPADD gets  ${LIBDO.libname}/liblibname.so  or
				    ${LIBDO.libname}/liblibname.a   added.

		The special value "_external" for LIBDO.lib makes the
		build system to assume the library comes from outside
		of the NetBSD source tree and only causes -llibname
		to be added to LDADD.

		This variable may be used for individual libraries/programs,
		as well as in parent directories to cache common libraries
		as a build-time optimization.

The include file <bsd.lib.mk> includes the file named "../Makefile.inc"
if it exists, as well as the include file <bsd.man.mk>.

It has rules for building profiled objects; profiled libraries are
built by default.

Libraries are ranlib'd when made.


=-=-=-=-=   bsd.links.mk   =-=-=-=-=

The include file <bsd.links.mk> handles the LINKS and SYMLINKS variables
and is included from <bsd.lib.mk> and <bsd.prog.mk>.

LINKSOWN, LINKSGRP, and LINKSMODE, are relevant only if a metadata log
is used. The defaults may be modified by other bsd.*.mk files which
include bsd.links.mk.  In the future, these variables may be replaced
by a method for explicitly recording hard links in a metadata log.

LINKS		The list of hard links, consisting of pairs of paths:
			source-file target-file
		${DESTDIR} is prepended to both paths before linking.
		For example, to link /bin/test and /bin/[, use:
			LINKS=/bin/test /bin/[

CONFIGLINKS	Similar semantics to LINKS, except that the links
		are installed by the `configinstall' target,
		not the `install' target.

SYMLINKS	The list of symbolic links, consisting of pairs of paths:
			source-file target-file
		${DESTDIR} is only prepended to target-file before linking.
		For example, to symlink /usr/bin/tar to /bin/tar resulting
		in ${DESTDIR}/usr/bin/tar -> /bin/tar:
			SYMLINKS=/bin/tar /usr/bin/tar

CONFIGSYMLINKS	Similar semantics to SYMLINKS, except that the symbolic links
		are installed by the `configinstall' target,
		not the `install' target.

LINKSOWN	Link owner.  [${BINOWN}]

LINKSGRP	Link group.  [${BINGRP}]

LINKSMODE	Link mode.  [${NONBINMODE}]

LINKSOWN_<fn>	Link owner of the specific file <fn>.

LINKSGRP_<fn>	Link group of the specific file <fn>.

LINKSMODE_<fn>	Link mode of the specific file <fn>.


=-=-=-=-=   bsd.man.mk   =-=-=-=-=

The include file <bsd.man.mk> handles installing manual pages and their
links.

It has a three targets:

	catinstall:
		Install the preformatted manual pages and their links.
	htmlinstall:
		Install the HTML manual pages and their links.
	maninstall:
		Install the manual page sources and their links.

It sets/uses the following variables:

MANDIR		Base path for manual installation.

MANGRP		Manual group.

MANOWN		Manual owner.

MANMODE		Manual mode.

MANSUBDIR	Subdirectory under the manual page section, i.e. "/vax"
		or "/tahoe" for machine specific manual pages.

MAN		The manual pages to be installed (use a .1 - .9 suffix).

MLINKS		List of manual page links (using a .1 - .9 suffix).  The
		linked-to file must come first, the linked file second,
		and there may be multiple pairs.

The include file <bsd.man.mk> includes a file named "../Makefile.inc" if
it exists.


=-=-=-=-=   bsd.obj.mk   =-=-=-=-=

The include file <bsd.obj.mk> defines targets related to the creation
and use of separated object and source directories.

If an environment variable named MAKEOBJDIRPREFIX is set, make(1) uses
${MAKEOBJDIRPREFIX}${.CURDIR} as the name of the object directory if
it exists.  Otherwise make(1) looks for the existence of a
subdirectory (or a symlink to a directory) of the source directory
into which built targets should be placed.  If an environment variable
named MAKEOBJDIR is set, make(1) uses its value as the name of the
object directory; failing that, make first looks for a subdirectory
named "obj.${MACHINE}", and if that doesn't exist, it looks for "obj".

Object directories are not created automatically by make(1) if they
don't exist; you need to run a separate "make obj".  (This will happen
during a top-level build if "MKOBJDIRS" is set to a value other than
"no").  When the source directory is a subdirectory of ${BSDSRCDIR} --
and this is determined by a simple string prefix comparison -- object
directories are created in a separate object directory tree, and a
symlink to the object directory in that tree is created in the source
directory; otherwise, "make obj" assumes that you're not in the main
source tree and that it's not safe to use a separate object tree.

Several variables used by <bsd.obj.mk> control exactly what
directories and links get created during a "make obj":

MAKEOBJDIR	If set, this is the component name of the object
		directory.

OBJMACHINE	If this is set but MAKEOBJDIR is not set, creates
		object directories or links named "obj.${MACHINE}";
		otherwise, just creates ones named "obj".

OBJMACHINE_ARCH If set with OBJMACHINE, creates object directories or
		links named "obj.${MACHINE}-${MACHINE_ARCH}".

USR_OBJMACHINE	If set, and the current directory is a subdirectory of
		${BSDSRCDIR}, create object directory in the
		corresponding subdirectory of ${BSDOBJDIR}.${MACHINE};
		otherwise, create it in the corresponding subdirectory
		of ${BSDOBJDIR}

BUILDID		If set, the contents of this variable are appended
		to the object directory name.  If OBJMACHINE is also
		set, ".${BUILDID}" is added after ".${MACHINE}".


=-=-=-=-=   bsd.prog.mk   =-=-=-=-=

The include file <bsd.prog.mk> handles building programs from one or
more source files, along with their manual pages.  It has a limited number
of suffixes, consistent with the current needs of the BSD tree.
<bsd.prog.mk> includes <bsd.shlib.mk> to get shared library parameters.

It has eight targets:

	all:
		build the program and its manual page.  This also
		creates a GDB initialization file (.gdbinit) in
		the objdir.  The .gdbinit file sets the shared library
		prefix to ${DESTDIR} to facilitate cross-debugging.
	clean:
		remove the program, any object files and the files a.out,
		Errs, errs, mklog, and ${PROG}.core.
	cleandir:
		remove all of the files removed by the target clean, as
		well as .depend, tags, and any manual pages.
		`distclean' is a synonym for `cleandir'.
	depend:
		make the dependencies for the source files, and store
		them in the file .depend.
	includes:
		install any header files.
	install:
		install the program and its manual pages; if the Makefile
		does not itself define the target install, the targets
		beforeinstall and afterinstall may also be used to cause
		actions immediately before and after the install target
		is executed.
	lint:
		run lint on the source files
	tags:
		create a tags file for the source files.

It sets/uses the following variables:

BINGRP		Binary group.

BINOWN		Binary owner.

BINMODE		Binary mode.

CLEANDIRFILES	Additional files to remove for the cleandir target.

CLEANFILES	Additional files to remove for the clean and cleandir targets.

CONFIGOPTS	Additional flags to config(1) when building kernels.

COPTS		Additional flags to the compiler when creating C objects.

COPTS.<fn>	Additional flags to the compiler when creating the
		C objects for <fn>.
		For <fn>.[ly], "<fn>.c" must be used.

CPUFLAGS	Additional flags to the compiler/assembler to select
		CPU instruction set options, CPU tuning options, etc.

CPUFLAGS.<fn>	Additional flags to the compiler/assembler for <fn>.
		For <fn>.[ly], "<fn>.c" must be used.

CPPFLAGS	Additional flags to the C pre-processor.

CPPFLAGS.<fn>	Additional flags to the C pre-processor for <fn>.
		For <fn>.[ly], "<fn>.c" must be used.

GDBINIT		List of GDB initialization files to add to "source"
		directives in the .gdbinit file that is created in the
		objdir.

LDADD		Additional loader objects.  Usually used for libraries.
		For example, to load with the compatibility and utility
		libraries, use:

			LDADD+=-lutil -lcompat

LDFLAGS		Additional linker flags (passed to ${CC} during link).

LINKS		See <bsd.links.mk>

OBJCOPTS	Additional flags to the compiler when creating ObjC objects.

OBJCOPTS.<fn>	Additional flags to the compiler when creating the
		ObjC objects for <fn>.
		For <fn>.[ly], "<fn>.c" must be used.

SYMLINKS	See <bsd.links.mk>

MAN		Manual pages (should end in .1 - .9).  If no MAN variable is
		defined, "MAN=${PROG}.1" is assumed.

PAXCTL_FLAGS	If defined, run paxctl(1) on the program binary after link
		time, with the value of this variable as args to paxctl(1).

PAXCTL_FLAGS.${PROG} Custom override for PAXCTL_FLAGS.

PROG		The name of the program to build.  If not supplied, nothing
		is built.

PROG_CXX	If defined, the name of the program to build.  Also
		causes <bsd.prog.mk> to link the program with the C++
		compiler rather than the C compiler.  PROG_CXX overrides
		the value of PROG if PROG is also set.

PROGNAME	The name that the above program will be installed as, if
		different from ${PROG}.

PROGS		Multiple programs to build from a single directory.
		Defaults to PROG. For each program ${_P} in ${PROGS},
		uses SRCS.${_P}, defaulting to ${_P}.c.

PROGS_CXX	Multiple C++ programs to build from a single directory.
		Defaults to PROG_CXX. For each program ${_P} in ${PROGS_CXX},
		uses SRCS.${_P}, defaulting to ${_P}.cc.

SRCS		List of source files to build the program.  If SRCS is not
		defined, it's assumed to be ${PROG}.c or ${PROG_CXX}.cc.

DPSRCS		List of source files which are needed for generating
		dependencies, but are not needed in ${SRCS}.

DPADD		Additional dependencies for the program.  Usually used for
		libraries.  For example, to depend on the compatibility and
		utility libraries use:

			DPADD+=${LIBCOMPAT} ${LIBUTIL}

		The following system libraries are predefined for DPADD:

		LIBARCHIVE?=		${DESTDIR}/usr/lib/libarchive.a
		LIBASN1?=		${DESTDIR}/usr/lib/libasn1.a
		LIBATF_C?=		${DESTDIR}/usr/lib/libatf-c.a
		LIBATF_CXX?=		${DESTDIR}/usr/lib/libatf-c++.a
		LIBBIND9?=		${DESTDIR}/usr/lib/libbind9.a
		LIBBLOCKLIST?=		${DESTDIR}/usr/lib/libblocklist.a
		LIBBLUETOOTH?=		${DESTDIR}/usr/lib/libbluetooth.a
		LIBBSDMALLOC?=		${DESTDIR}/usr/lib/libbsdmalloc.a
		LIBBZ2?=		${DESTDIR}/usr/lib/libbz2.a
		LIBC?=			${DESTDIR}/usr/lib/libc.a
		LIBC_PIC?=		${DESTDIR}/usr/lib/libc_pic.a
		LIBCBOR?=		${DESTDIR}/usr/lib/libcbor.a
		LIBCOMPAT?=		${DESTDIR}/usr/lib/libcompat.a
		LIBCOM_ERR?=		${DESTDIR}/usr/lib/libcom_err.a
		LIBCRYPT?=		${DESTDIR}/usr/lib/libcrypt.a
		LIBCRYPTO?=		${DESTDIR}/usr/lib/libcrypto.a
		LIBCURSES?=		${DESTDIR}/usr/lib/libcurses.a
		LIBCXX?=		${DESTDIR}/usr/lib/libc++.a
		LIBDES?=		${DESTDIR}/usr/lib/libdes.a
		LIBDNS?=		${DESTDIR}/usr/lib/libdns.a
		LIBEDIT?=		${DESTDIR}/usr/lib/libedit.a
		LIBEVENT?=		${DESTDIR}/usr/lib/libevent.a
		LIBEVENT_OPENSSL?=	${DESTDIR}/usr/lib/libevent_openssl.a
		LIBEVENT_PTHREADS?=	${DESTDIR}/usr/lib/libevent_pthreads.a
		LIBEXECINFO?=		${DESTDIR}/usr/lib/libexecinfo.a
		LIBEXPAT?=		${DESTDIR}/usr/lib/libexpat.a
		LIBFETCH?=		${DESTDIR}/usr/lib/libfetch.a
		LIBFIDO2?=		${DESTDIR}/usr/lib/libfido2.a
		LIBFL?=			${DESTDIR}/usr/lib/libfl.a
		LIBFORM?=		${DESTDIR}/usr/lib/libform.a
		LIBGCC?=		${DESTDIR}/usr/lib/libgcc.a
		LIBGNUCTF?=		${DESTDIR}/usr/lib/libgnuctf.a
		LIBGNUMALLOC?=		${DESTDIR}/usr/lib/libgnumalloc.a
		LIBGSSAPI?=		${DESTDIR}/usr/lib/libgssapi.a
		LIBHDB?=		${DESTDIR}/usr/lib/libhdb.a
		LIBHEIMBASE?=		${DESTDIR}/usr/lib/libheimbase.a
		LIBHEIMNTLM?=		${DESTDIR}/usr/lib/libheimntlm.a
		LIBHX500?=		${DESTDIR}/usr/lib/libhx500.a
		LIBINTL?=		${DESTDIR}/usr/lib/libintl.a
		LIBIPSEC?=		${DESTDIR}/usr/lib/libipsec.a
		LIBISC?=		${DESTDIR}/usr/lib/libisc.a
		LIBISCCC?=		${DESTDIR}/usr/lib/libisccc.a
		LIBISCFG?=		${DESTDIR}/usr/lib/libiscfg.a
		LIBKADM5CLNT?=		${DESTDIR}/usr/lib/libkadm5clnt.a
		LIBKADM5SRV?=		${DESTDIR}/usr/lib/libkadm5srv.a
		LIBKAFS?=		${DESTDIR}/usr/lib/libkafs.a
		LIBKRB5?=		${DESTDIR}/usr/lib/libkrb5.a
		LIBKVM?=		${DESTDIR}/usr/lib/libkvm.a
		LIBL?=			${DESTDIR}/usr/lib/libl.a
		LIBLBER?=		${DESTDIR}/usr/lib/liblber.a
		LIBLDAP?=		${DESTDIR}/usr/lib/libldap.a
		LIBLDAP_R?=		${DESTDIR}/usr/lib/libldap_r.a
		LIBLUA?=		${DESTDIR}/usr/lib/liblua.a
		LIBM?=			${DESTDIR}/usr/lib/libm.a
		LIBMAGIC?=		${DESTDIR}/usr/lib/libmagic.a
		LIBMENU?=		${DESTDIR}/usr/lib/libmenu.a
		LIBNETPGPVERIFY?=	${DESTDIR}/usr/lib/libnetpgpverify.a
		LIBNS?=			${DESTDIR}/usr/lib/libns.a
		LIBOBJC?=		${DESTDIR}/usr/lib/libobjc.a
		LIBOSSAUDIO?=		${DESTDIR}/usr/lib/libossaudio.a
		LIBPAM?=		${DESTDIR}/usr/lib/libpam.a
		LIBPANEL?=		${DESTDIR}/usr/lib/libpanel.a
		LIBPCAP?=		${DESTDIR}/usr/lib/libpcap.a
		LIBPCI?=		${DESTDIR}/usr/lib/libpci.a
		LIBPOSIX?=		${DESTDIR}/usr/lib/libposix.a
		LIBPTHREAD?=		${DESTDIR}/usr/lib/libpthread.a
		LIBPUFFS?=		${DESTDIR}/usr/lib/libpuffs.a
		LIBQUOTA?=		${DESTDIR}/usr/lib/libquota.a
		LIBRADIUS?=		${DESTDIR}/usr/lib/libradius.a
		LIBREFUSE?=		${DESTDIR}/usr/lib/librefuse.a
		LIBRESOLV?=		${DESTDIR}/usr/lib/libresolv.a
		LIBRMT?=		${DESTDIR}/usr/lib/librmt.a
		LIBROKEN?=		${DESTDIR}/usr/lib/libroken.a
		LIBRPCSVC?=		${DESTDIR}/usr/lib/librpcsvc.a
		LIBRT?=			${DESTDIR}/usr/lib/librt.a
		LIBRUMP?=		${DESTDIR}/usr/lib/librump.a
		LIBRUMPFS_CD9660?=	${DESTDIR}/usr/lib/librumpfs_cd9660.a
		LIBRUMPFS_EFS?=		${DESTDIR}/usr/lib/librumpfs_efs.a
		LIBRUMPFS_EXT2FS?=	${DESTDIR}/usr/lib/librumpfs_ext2fs.a
		LIBRUMPFS_FFS?=		${DESTDIR}/usr/lib/librumpfs_ffs.a
		LIBRUMPFS_HFS?=		${DESTDIR}/usr/lib/librumpfs_hfs.a
		LIBRUMPFS_LFS?=		${DESTDIR}/usr/lib/librumpfs_lfs.a
		LIBRUMPFS_MSDOS?=	${DESTDIR}/usr/lib/librumpfs_msdos.a
		LIBRUMPFS_NFS?=		${DESTDIR}/usr/lib/librumpfs_nfs.a
		LIBRUMPFS_NTFS?=	${DESTDIR}/usr/lib/librumpfs_ntfs.a
		LIBRUMPFS_SYSPUFFS?=	${DESTDIR}/usr/lib/librumpfs_syspuffs.a
		LIBRUMPFS_TMPFS?=	${DESTDIR}/usr/lib/librumpfs_tmpfs.a
		LIBRUMPFS_UDF?=		${DESTDIR}/usr/lib/librumpfs_udf.a
		LIBRUMPUSER?=		${DESTDIR}/usr/lib/librumpuser.a
		LIBSASLC?=		${DESTDIR}/usr/lib/libsaslc.a
		LIBSKEY?=		${DESTDIR}/usr/lib/libskey.a
		LIBSL?=			${DESTDIR}/usr/lib/libsl.a
		LIBSQLITE3?=		${DESTDIR}/usr/lib/libsqlite3.a
		LIBSSH?=		${DESTDIR}/usr/lib/libssh.a
		LIBSSL?=		${DESTDIR}/usr/lib/libssl.a
		LIBSTDCXX?=		${DESTDIR}/usr/lib/libstdc++.a
		LIBSUPCXX?=		${DESTDIR}/usr/lib/libsupc++.a
		LIBTERMINFO?=		${DESTDIR}/usr/lib/libterminfo.a
		LIBTRE?=		${DESTDIR}/usr/lib/libtre.a
		LIBUNBOUND?=		${DESTDIR}/usr/lib/libunbound.a
		LIBUSBHID?=		${DESTDIR}/usr/lib/libusbhid.a
		LIBUTIL?=		${DESTDIR}/usr/lib/libutil.a
		LIBWIND?=		${DESTDIR}/usr/lib/libwind.a
		LIBWRAP?=		${DESTDIR}/usr/lib/libwrap.a
		LIBY?=			${DESTDIR}/usr/lib/liby.a
		LIBZ?=			${DESTDIR}/usr/lib/libz.a

		The following c startup files.

		LIBCRT0?=		${DESTDIR}/usr/lib/crt0.o
		LIBCRTI?=		${DESTDIR}/usr/lib/crti.o
		LIBCRTBEGIN?=		${DESTDIR}/usr/lib/crti.o
		LIBCRTEND?=		${DESTDIR}/usr/lib/crtn.o

		The following X-Windows libraries are predefined for DPADD:

		LIBDPS?=		${DESTDIR}/usr/X11R7/lib/libdps.a
		LIBFNTSTUBS?=		${DESTDIR}/usr/X11R7/lib/libfntstubs.a
		LIBFONTCACHE?=		${DESTDIR}/usr/X11R7/lib/libfontcache.a
		LIBFONTCONFIG?=		${DESTDIR}/usr/X11R7/lib/libfontconfig.a
		LIBFONTENC?=		${DESTDIR}/usr/X11R7/lib/libfontenc.a
		LIBFREETYPE?=		${DESTDIR}/usr/X11R7/lib/libfreetype.a
		LIBFS?=			${DESTDIR}/usr/X11R7/lib/libFS.a
		LIBGL?=			${DESTDIR}/usr/X11R7/lib/libGL.a
		LIBGLU?=		${DESTDIR}/usr/X11R7/lib/libGLU.a
		LIBICE?=		${DESTDIR}/usr/X11R7/lib/libICE.a
		LIBLBXUTIL?=		${DESTDIR}/usr/X11R7/lib/liblbxutil.a
		LIBSM?=			${DESTDIR}/usr/X11R7/lib/libSM.a
		LIBX11?=		${DESTDIR}/usr/X11R7/lib/libX11.a
		LIBX11_XCB?=		${DESTDIR}/usr/X11R7/lib/libX11-xcb.a
		LIBXAU?=		${DESTDIR}/usr/X11R7/lib/libXau.a
		LIBXAW?=		${DESTDIR}/usr/X11R7/lib/libXaw.a
		LIBXCB?=		${DESTDIR}/usr/X11R7/lib/libxcb.a
		LIBXCOMPOSITE?=		${DESTDIR}/usr/X11R7/lib/libXcomposite.a
		LIBXCVT?=		${DESTDIR}/usr/X11R7/lib/libxcvt.a
		LIBXDAMAGE?=		${DESTDIR}/usr/X11R7/lib/libXdamage.a
		LIBXDMCP?=		${DESTDIR}/usr/X11R7/lib/libXdmcp.a
		LIBXEXT?=		${DESTDIR}/usr/X11R7/lib/libXext.a
		LIBXFIXES?=		${DESTDIR}/usr/X11R7/lib/libXfixes.a
		LIBXFONT2?=		${DESTDIR}/usr/X11R7/lib/libXfont2.a
		LIBXFONT?=		${DESTDIR}/usr/X11R7/lib/libXfont.a
		LIBXFT?=		${DESTDIR}/usr/X11R7/lib/libXft.a
		LIBXI?=			${DESTDIR}/usr/X11R7/lib/libXi.a
		LIBXINERAMA?=		${DESTDIR}/usr/X11R7/lib/libXinerama.a
		LIBXKBFILE?=		${DESTDIR}/usr/X11R7/lib/libxkbfile.a
		LIBXMU?=		${DESTDIR}/usr/X11R7/lib/libXmu.a
		LIBXMUU?=		${DESTDIR}/usr/X11R7/lib/libXmuu.a
		LIBXPM?=		${DESTDIR}/usr/X11R7/lib/libXpm.a
		LIBXRANDR?=		${DESTDIR}/usr/X11R7/lib/libXrandr.a
		LIBXRENDER?=		${DESTDIR}/usr/X11R7/lib/libXrender.a
		LIBXSS?=		${DESTDIR}/usr/X11R7/lib/libXss.a
		LIBXT?=			${DESTDIR}/usr/X11R7/lib/libXt.a
		LIBXTRAP?=		${DESTDIR}/usr/X11R7/lib/libXTrap.a
		LIBXTST?=		${DESTDIR}/usr/X11R7/lib/libXtst.a
		LIBXV?=			${DESTDIR}/usr/X11R7/lib/libXv.a
		LIBXXF86DGA?=		${DESTDIR}/usr/X11R7/lib/libXxf86dga.a
		LIBXXF86MISC?=		${DESTDIR}/usr/X11R7/lib/libXxf86misc.a
		LIBXXF86VM?=		${DESTDIR}/usr/X11R7/lib/libXxf86vm.a

STRIPFLAG	The flag passed to the install program to cause the binary
		to be stripped.

SUBDIR		A list of subdirectories that should be built as well.
		Each of the targets will execute the same target in the
		subdirectories.

SCRIPTS		A list of interpreter scripts [file.{sh,csh,pl,awk,...}].
		These are installed exactly like programs.

SCRIPTSDIR	The location to install the scripts.  Each script can be
		installed to a separate path by setting SCRIPTSDIR_<script>.

SCRIPTSNAME	The name that the above program will be installed as, if
		different from ${SCRIPTS}. These can be further specialized
		by setting SCRIPTSNAME_<script>.

FILES		See description of <bsd.files.mk>.

SHLINKDIR	Target directory for shared linker.  See description of
		<bsd.own.mk> for additional information about this variable.

The include file <bsd.prog.mk> includes the file named "../Makefile.inc"
if it exists, as well as the include file <bsd.man.mk>.

Some simple examples:

To build foo from foo.c with a manual page foo.1, use:

	PROG=	foo

	.include <bsd.prog.mk>

To build foo from foo.c with a manual page foo.2, add the line:

	MAN=	foo.2

If foo does not have a manual page at all, add the line:

	MKMAN=	no

If foo has multiple source files, add the line:

	SRCS=	a.c b.c c.c d.c


=-=-=-=-=   bsd.rpc.mk   =-=-=-=-=

The include file <bsd.rpc.mk> contains a makefile fragment used to
construct source files built by rpcgen.

The following macros may be defined in makefiles which include
<bsd.rpc.mk> in order to control which files get built and how they
are to be built:

RPC_INCS	construct .h file from .x file
RPC_XDRFILES	construct _xdr.c from .x file
		(for marshalling/unmarshalling data types)
RPC_SVCFILES	construct _svc.c from .x file
		(server-side stubs)
RPC_SVCFLAGS	Additional flags passed to builds of RPC_SVCFILES.

RPC_XDIR	Directory containing .x/.h files


=-=-=-=-=   bsd.shlib.mk   =-=-=-=-=

The include file <bsd.shlib.mk> computes parameters for shared library
installation and use.  It defines no targets.  <bsd.own.mk> MUST be
included before <bsd.shlib.mk>.

<bsd.own.mk> sets the following variables, if they are not already defined
(defaults are in brackets):

SHLIBINSTALLDIR If ${USE_SHLIBDIR} is not "no", use ${SHLIBINSTALLDIR}
		instead of ${LIBDIR} as the base path for shared library
		installation.  [/lib]

SHLIBDIR	The path to USE_SHLIBDIR shared libraries to use when building
		a program.  [/lib for programs in /bin and /sbin, /usr/lib
		for all others.]

_LIBSODIR	Set to ${SHLIBINSTALLDIR} if ${USE_SHLIBDIR} is not "no",
		otherwise set to ${LIBDIR}

SHLINKINSTALLDIR Base path for shared linker.  [/libexec]

SHLINKDIR	Path to use for shared linker when building a program.
		[/libexec for programs in /bin and /sbin, /usr/libexec for
		all others.]


=-=-=-=-=   bsd.subdir.mk   =-=-=-=-=

The include file <bsd.subdir.mk> contains the default targets for building
subdirectories.  It has the same eight targets as <bsd.prog.mk>: all,
clean, cleandir, depend, includes, install, lint, and tags.  It uses the
following variables:

NOSUBDIR	If this variable is defined, then the SUBDIR variable
		will be ignored and subdirectories will not be processed.

SUBDIR		For all of the directories listed in ${SUBDIR}, the
		specified directory will be visited and the target made.

		As a special case, the use of a token .WAIT as an
		entry in SUBDIR acts as a synchronization barrier
		when multiple make jobs are run; subdirs before the
		.WAIT must complete before any subdirs after .WAIT are
		started.  See make(1) for some caveats on use of .WAIT
		and other special sources.


=-=-=-=-=   bsd.x11.mk   =-=-=-=-=

The include file <bsd.x11.mk> contains parameters and targets for
cross-building X11 from ${X11SRCDIR.<package>}.  It should be included
after the general Makefile contents but before the include files such as
<bsd.prog.mk> and <bsd.lib.mk>.

It provides the following targets:
	.man.1 .man.3 .man.4 .man.5 .man.7:
		If ${MAN} or ${PROG} is set and ${MKMAN} != "no",
		these rules convert from X11's manual page source
		into an mdoc.old source file.

It sets the following variables:

BINDIR			Set to ${X11BINDIR}.
			To override, define after including <bsd.x11.mk>

LIBDIR			Set to ${X11USRLIBDIR}.
			To override, define after including <bsd.x11.mk>

MANDIR			Set to ${X11MANDIR}.
			To override, define after including <bsd.x11.mk>

CPPFLAGS		Appended with definitions to include from
			${DESTDIR}${X11INCDIR}

LDFLAGS			Appended with definitions to link from
			${DESTDIR}${X11USRLIBDIR}

X11FLAGS.CONNECTION	Equivalent to X11's CONNECTION_FLAGS.

X11FLAGS.EXTENSION	Equivalent to X11's EXT_DEFINES.

X11FLAGS.LOADABLE	Equivalent to X11's LOADABLE.

X11FLAGS.OS_DEFINES	Equivalent to X11's OS_DEFINES.

X11FLAGS.SERVER		Equivalent to X11's ServerDefines.

X11FLAGS.THREADLIB	Equivalent to X11's THREADS_DEFINES for libraries.

X11FLAGS.THREADS	Equivalent to X11's THREADS_DEFINES.

X11FLAGS.VERSION	cpp(1) definitions of OSMAJORVERSION and OSMINORVERSION.

X11FLAGS.DIX		Equivalent to X11's DIX_DEFINES.

X11TOOL_UNXCOMM		Commandline to convert `XCOMM' comments to `#'

It uses the following variables:

APPDEFS			List of app-default files to install.

CPPSCRIPTS		List of files/scripts to run through cpp(1)
			and then ${X11TOOL_UNXCOMM}.  The source files
			have a `.cpp' suffix, the generated files do not.

CPPSCRIPTFLAGS		Additional flags to cpp(1) when building CPPSCRIPTS.

CPPSCRIPTFLAGS_<fn>	Additional flags to cpp(1) when building CPPSCRIPT <fn>.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The following files are described here for completion, but they are not
supposed to be included directly from other Makefiles; they are used
internally by other system files.

=-=-=-=-=   bsd.sys.mk   =-=-=-=-=

The include file <bsd.sys.mk> is used by other system mk files and
it is not intended to be included standalone. It contains rules and
system build variables. It requires bsd.own.mk to be included first.
It contains overrides that are used when building the NetBSD source tree.

The following variables control how various files are compiled/built.
(Note that these may be overridden in <bsd.own.mk> if USETOOLS == "yes"):

AR		Create, modify, and extract from archives.  [ar]

ARFLAGS		Options to ${AR}.  [rl]

ARM_ELF2AOUT	Convert ELF-format executable to a.out.  [elf2aout]

AS		Assembler.  [as]

AFLAGS		Options to ${CC} when compiling or linking .s or .S
		assembly source files.  []

BUILDSEED	GCC uses random numbers when compiling C++ code.
		If this option is present, seed the random number
		generator based on the value, source file names and
		the output file name to make builds more deterministic.
		Additional information is available in the GCC
		documentation of -frandom-seed.

CC		C compiler.  [cc]

CFLAGS		Options to ${CC}.  [Usually -O or -O2]

CPP		C Pre-Processor.  [cpp]

CPPFLAGS	Options to ${CPP}.  []

CPUFLAGS	Optimization flags for ${CC}.  []

CXX		C++ compiler.  [c++]

CXXFLAGS	Options to ${CXX}.  [${CFLAGS}]

M68K_ELF2AOUT	Convert ELF-format executable to a.out.  [elf2aout]

MIPS_ELF2ECOFF	Convert ELF-format executable to ECOFF.  [elf2ecoff]

FC		Fortran compiler.  [f77]

FFLAGS		Options to {$FC}.  [-O]

HOST_SH		Shell.  This must be an absolute path, because it may be
		substituted into "#!" lines in scripts.  [/bin/sh]

INSTALL		install(1) command.  [install]

LEX		Lexical analyzer.  [lex]

LFLAGS		Options to ${LEX}.  []

LPREFIX		Symbol prefix for ${LEX} (see -P option in lex(1)) [yy]

LD		Linker.  [ld]

LDFLAGS		Options to ${CC} during the link process.  []

LINT		C program verifier.  [lint]

LINTFLAGS	Options to ${LINT}.  [-chapbrxzgFS]

LORDER		List dependencies for object files.  [lorder]

MAKE		make(1).  [make]

MKDEP		Construct Makefile dependency list.  [mkdep]

MKDEPCXX	Construct Makefile dependency list for C++ files.  [mkdep]

NM		List symbols from object files.  [nm]

PC		Pascal compiler.  [pc]	(Not present)

PFLAGS		Options to ${PC}.  []

OBJC		Objective C compiler.  [${CC}]

OBJCFLAGS	Options to ${OBJC}.  [${CFLAGS}]

OBJCOPY		Copy and translate object files.  [objcopy]

OBJCOPYLIBFLAGS Flags to pass to objcopy when library objects are
		being built. [${.TARGET} =~ "*.po" ? -X : -x]

OBJDUMP		Display information from object files.  [objdump]

RANLIB		Generate index to archive.  [ranlib]

READELF		Display information from ELF object files.  [readelf]

SIZE		List section sizes and total size.  [size]

STRINGS		Display printable character sequences in files.  [strings]

STRIP		Discard symbols from object files.  [strip]

TSORT		Topological sort of a directed graph.  [tsort -q]

YACC		LALR(1) parser generator.  [yacc]

YFLAGS		Options to ${YACC}.  []

YHEADER		If defined, add "-d" to YFLAGS, and add dependencies
		from <file>.y to <file>.h and <file>.c, and add
		<foo>.h to CLEANFILES.

YPREFIX		If defined, add "-p ${YPREFIX}" to YFLAGS.


Other variables of note (incomplete list):

NOCLANGERROR	If defined and clang is used as C compiler, -Werror is not
		passed to it.

NOGCCERROR	If defined, prevents passing certain ${CFLAGS} to GCC
		that cause warnings to be fatal, such as:
			-Werror -Wa,--fatal-warnings
		(The latter being for as(1).)

WARNS		Crank up compiler warning options; the distinct levels are:
			WARNS=1
			WARNS=2
			WARNS=3
			WARNS=4
			WARNS=5
			WARNS=6

=-=-=-=-=   bsd.host.mk   =-=-=-=-=

This file is automatically included from bsd.own.mk. It contains settings
for all the HOST_* variables that are used in host programs and libraries.

HOST_AR			The host archive processing command

HOST_CC			The host c compiler

HOST_CFLAGS		The host c compiler flags

HOST_COMPILE.c		The host c compiler line with flags

HOST_COMPILE.cc		The host c++ compiler line with flags

HOST_CPP		The host c pre-processor

HOST_CPPFLAGS		The host c pre-processor flags

HOST_CXX		The host c++ compiler

HOST_CXXFLAGS		The host c++ compiler flags

HOST_INSTALL_DIR	The host command to install a directory

HOST_INSTALL_FILE	The host command to install a file

HOST_INSTALL_SYMLINK	The host command to install a symlink

HOST_LD			The host linker command

HOST_LDFLAGS		The host linker flags

HOST_LINK.c		The host c linker line with flags

HOST_LINK.cc		The host c++ linker line with flags

HOST_LN			The host command to link two files

HOST_MKDEP		The host command to create dependencies for c programs

HOST_MKDEPCXX		The host command to create dependencies for c++ programs

HOST_OSTYPE		The host OSNAME-RELEASE-ARCH tupple

HOST_RANLIB		The host command to create random access archives

HOST_SH			The host Bourne shell interpreter name (absolute path)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=