Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. =================================================================== RCS file: /ftp/cvs/cvsroot/src/BUILDING,v rcsdiff: /ftp/cvs/cvsroot/src/BUILDING,v: warning: Unknown phrases like `commitid ...;' are present. retrieving revision 1.37 retrieving revision 1.61 diff -u -p -r1.37 -r1.61 --- src/BUILDING 2003/07/18 02:19:55 1.37 +++ src/BUILDING 2007/03/26 17:35:06 1.61 @@ -1,7 +1,7 @@ BUILDING(8) NetBSD System Manager's Manual BUILDING(8) NAME - BUILDING - Procedure for building NetBSD from source code. + BUILDING -- Procedure for building NetBSD from source code. STATUS This document is a work-in-progress. As such, the information described @@ -9,8 +9,8 @@ STATUS Once this document is completely in sync with reality, this paragraph will be removed. - Discrepancies between this documentation and the current reality of im- - plementation are noted specially, as with the note below: + Discrepancies between this documentation and the current reality of + implementation are noted specially, as with the note below: Note: This document applies only to platforms which use the new toolchain as indicated by the default setting of TOOLCHAIN_MISSING in . @@ -28,12 +28,8 @@ REQUIREMENTS host system to create a build toolchain for the target architecture. The host system must have at least C and C++ compilers in order to create the toolchain (make is not required); all other tools are created as part of - the NetBSD build process. - - Note: A couple of host toolchain components are not yet available - in the tools directory. Also, some tools use non-POSIX, non-ANSI C - extensions and need to be standardized. As a result, cross-compil- - ing from systems other than NetBSD is not currently supported. + the NetBSD build process. (See the environment variables section below + if you need to override or manually select your compilers.) FILES Source tree layout @@ -42,8 +38,12 @@ FILES BUILDING This document (in plaintext). - Makefile The main Makefile for NetBSD; should only be run for na- - tive builds with an appropriately up-to-date version of + tools/compat/README + Special notes for cross-hosting a NetBSD build on non- + NetBSD platforms. + + Makefile The main Makefile for NetBSD; should only be run for + native builds with an appropriately up-to-date version of NetBSD make(1). (For building from out-of-date systems or on a non-native host, see the build.sh shell script.) @@ -61,8 +61,8 @@ FILES Sources imported verbatim from third parties, without man- gling the existing build structure. Other source trees in bin through usr.sbin use the NetBSD make(1) ``reachover'' - Makefile semantics when building these programs for a na- - tive host. + Makefile semantics when building these programs for a + native host. distrib/, etc/ Sources for items used when making a full release snap- @@ -83,6 +83,9 @@ FILES any of these directories are missing, they will be skipped during the build. + x11/ ``Reachover'' build structure for X11R6; the source is in + X11SRCDIR. + Build tree layout The NetBSD build tree is described in hier(7), and the release layout is described in release(7). @@ -91,6 +94,22 @@ CONFIGURATION Environment variables Several environment variables control the behaviour of NetBSD builds. + HOST_SH Path name to a POSIX-compliant shell. If this is not + set explicitly, then the default is set using heuris- + tics dependent on the host platform, or from the shell + under which build.sh is executed (if that can be deter- + mined), or using the first copy of sh found in PATH. + If the host system's /bin/sh is not POSIX-compliant, we + suggest that you build using commands like + + HOST_SH=/path/to/working/shell + export HOST_SH + ${HOST_SH} build.sh [options] + + HOST_CC Path name to C compiler used to create the toolchain. + + HOST_CXX Path name to C++ compiler used to create the toolchain. + MACHINE Machine type. MACHINE_ARCH Machine architecture. @@ -100,15 +119,17 @@ CONFIGURATION MAKEFLAGS Flags to invoke make(1) with. MAKEOBJDIR Directory to use as the .OBJDIR for the current direc- - tory. Used only if MAKEOBJDIRPREFIX is not defined. + tory. The value is subjected to variable expansion by + make(1). Used only if MAKEOBJDIRPREFIX is not defined. MAKEOBJDIR can only be provided in the environment or - via the -M flag of build.sh. + via the -O flag of build.sh. MAKEOBJDIRPREFIX Top level directory of the object directory tree. If - this is defined, ${MAKEOBJDIRPREFIX}/${.CURDIR} is used - as the .OBJDIR for the current directory. The current - directory may be read only. MAKEOBJDIRPREFIX can only - be provided in the environment or via the -M flag of + specified, must be an absolute path. If this is + defined, ${MAKEOBJDIRPREFIX}/${.CURDIR} is used as the + .OBJDIR for the current directory. The current direc- + tory may be read only. MAKEOBJDIRPREFIX can only be + provided in the environment or via the -M flag of build.sh. "make" variables @@ -124,11 +145,11 @@ CONFIGURATION DESTDIR Directory to contain the built NetBSD system. If set, spe- cial options are passed to the compilation tools to prevent their default use of the host system's /usr/include, - /usr/lib, and so forth. This pathname should not end with a - slash (/) character (for installation into the system's root - directory, set DESTDIR to an empty string). The directory - must reside on a file system which supports long file names - and hard links. + /usr/lib, and so forth. This pathname must be an absolute + path, and should not end with a slash (/) character. (For + installation into the system's root directory, set DESTDIR to + an empty string, not to ``/''). The directory must reside on + a file system which supports long file names and hard links. Default: Empty string if USETOOLS is ``yes''; unset other- wise. @@ -141,6 +162,18 @@ CONFIGURATION Default: ``/etc/mk.conf'' + MAKEVERBOSE + Level of verbosity of status messages. Supported values: + + 0 No descriptive messages are shown. + + 1 Descriptive messages are shown. + + 2 Descriptive messages (prefixed with a `#') and command + output is not suppressed. + + Default: 2 + MKCATPAGES Can be set to ``yes'' or ``no''. Indicates whether prefor- matted plaintext manual pages will be created during a build. @@ -149,14 +182,14 @@ CONFIGURATION MKCRYPTO Can be set to ``yes'' or ``no''. Indicates whether crypto- graphic code will be included in a build; provided for the benefit of countries that do not allow strong cryptography. - Will not affect use of the standard low-security password en- - cryption system, crypt(3). + Will not affect use of the standard low-security password + encryption system, crypt(3). Default: ``yes'' MKDOC Can be set to ``yes'' or ``no''. Indicates whether system - documentation destined for DESTDIR/usr/share/doc will be in- - stalled during a build. + documentation destined for DESTDIR/usr/share/doc will be + installed during a build. Default: ``yes'' @@ -190,8 +223,8 @@ CONFIGURATION Default: ``yes'' MKNLS Can be set to ``yes'' or ``no''. Indicates whether Native - Language System locale zone files will be compiled and in- - stalled during a build. + Language System locale zone files will be compiled and + installed during a build. Default: ``yes'' @@ -212,8 +245,8 @@ CONFIGURATION MKPICINSTALL Can be set to ``yes'' or ``no''. Indicates whether the ar(1) - format libraries (lib*_pic.a), used to generate shared li- - braries, are installed during a build. + format libraries (lib*_pic.a), used to generate shared + libraries, are installed during a build. Default: ``yes'' @@ -226,36 +259,49 @@ CONFIGURATION code. MKSHARE Can be set to ``yes'' or ``no''. Indicates whether files - destined to reside in DESTDIR/usr/share will be built and in- - stalled during a build. If set to ``no'', then all of + destined to reside in DESTDIR/usr/share will be built and + installed during a build. If set to ``no'', then all of MKCATPAGES, MKDOC, MKINFO, MKMAN, and MKNLS will be set to ``no'' unconditionally. Default: ``yes'' - TOOLDIR Directory to hold the host tools, once built. This directory - should be unique to a given host system and NetBSD source - tree. (However, multiple targets may share the same TOOLDIR; - the target-dependent files have unique names.) If unset, a - default based on the uname(1) information of the host plat- - form will be created in the .OBJDIR of src/tools. + MKTTINTERP Can be set to ``yes'' or ``no''. For X builds, decides if + the TrueType bytecode interpreter is turned on. See + http://www.freetype.org/patents.html for details. - Default: Unset. + Default: ``no'' - UNPRIVED If set, then an unprivileged install will occur. The user, - group, permissions, and file flags, will not be set on the - installed item; 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. + MKUNPRIVED Can be set to ``yes'' or ``no''. Indicates whether an + unprivileged install will occur. The user, group, permis- + sions, 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 are used + during the generation of the distribution tar files to ensure + that the appropriate file ownership is stored. - Default: Unset. + Default: ``no'' - UPDATE If set, then 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. This also has implications on full builds (see next - subsection). + 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. This also has + implications on full builds (see next subsection). + + Default: ``no'' + + MKX11 Can be set to ``yes'' or ``no''. Indicates whether X11R6 is + built from X11SRCDIR. + + Default: ``no'' + + TOOLDIR Directory to hold the host tools, once built. If specified, + must be an absolute path. This directory should be unique to + a given host system and NetBSD source tree. (However, multi- + ple targets may share the same TOOLDIR; the target-dependent + files have unique names.) If unset, a default based on the + uname(1) information of the host platform will be created in + the .OBJDIR of src. Default: Unset. @@ -279,24 +325,37 @@ CONFIGURATION Default: ``yes'' if building all or part of a whole NetBSD source tree (detected automatically); ``no'' otherwise (to - preserve traditional semantics of the make(1) in- - clude files). + preserve traditional semantics of the make(1) + include files). + + X11SRCDIR Directory containing the X11R6 source. If specified, must be + an absolute path. The main X11R6 source is found in + X11SRCDIR/xfree/xc. + + Default: ``/usr/xsrc'' "make" variables for full builds These variables only affect the top level ``Makefile'' and do not affect manually building subtrees of the NetBSD source code. INSTALLWORLDDIR Location for the ``make installworld'' target to install - to. + to. If specified, must be an absolute path. Default: ``/'' - MKOBJDIRS Can be set to ``yes'' or ``no''. Indicates whether ob- - ject directories will be created automatically (via a + 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. Default: ``no'' + MKUPDATE Can be set to ``yes'' or ``no''. If set, then in addi- + tion to the effects described for MKUPDATE=yes above, + this implies the effects of NOCLEANDIR (i.e., ``make + cleandir'' is avoided). + + Default: ``no'' + NBUILDJOBS Now obsolete. Use the make(1) option -j, instead (see below) @@ -319,34 +378,31 @@ CONFIGURATION NOINCLUDES If set, avoids the ``make includes'' phase of a full build. This has the effect of preventing make(1) from - thinking that some programs are out-of-date simply be- - cause the system include files have changed. However, + thinking that some programs are out-of-date simply + because the system include files have changed. However, this option should not be used when updating the entire NetBSD source tree arbitrarily; it is suggested to use - UPDATE in that case. + MKUPDATE=yes in that case. Default: Unset. RELEASEDIR If set, specifies the directory to which a release(7) layout will be written at the end of a ``make release''. + If specified, must be an absolute path. Default: Unset. Note: build.sh will provide a default of releasedir (in the top-level .OBJDIR) unless run in `expert' mode - UPDATE If set, then in addition to the effects described for - UPDATE above, this implies the effects of NOCLEANDIR - (i.e., ``make cleandir'' is avoided). - BUILDING "make" command line options - This is only a summary of options available to make(1); only the options - used most frequently with NetBSD builds are listed here. + This is not a summary of all the options available to make(1); only the + options used most frequently with NetBSD builds are listed here. -j njob Run up to njob make(1) subjobs in parallel. Makefiles should - use .WAIT or have explicit dependancies as necessary to en- - force build ordering. If you see build failures with -j, + use .WAIT or have explicit dependencies as necessary to + enforce build ordering. If you see build failures with -j, please save complete build logs so the failures can be ana- lyzed. @@ -360,7 +416,7 @@ BUILDING actually execute them. This will still cause recursion to take place. - -v var Print make(1)'s idea of the value of var. Does not build any + -V var Print make(1)'s idea of the value of var. Does not build any targets. var=value Set the variable var to value, overriding any setting speci- @@ -377,14 +433,12 @@ BUILDING clean Remove program and library object code files. - cleandir Same as clean, but also remove preformatted documentation, de- - pendency files generated by ``make depend'', and any other - files known to be created at build time. ``make distclean'' - may be used as a synonym, for familiarity with a similar well- - known convention. + cleandir Same as clean, but also remove preformatted documentation, + dependency files generated by ``make depend'', and any other + files known to be created at build time. - depend Create dependency files (.depend) containing more detailed in- - formation about the dependencies of source code on header + depend Create dependency files (.depend) containing more detailed + information about the dependencies of source code on header files. Allows programs to be recompiled automatically when a dependency changes. @@ -392,8 +446,10 @@ BUILDING This improves cache locality of the build since both passes read the source files in their entirety. - includes Build and install system header files. Typically needed be- - fore any system libraries or programs can be built. + distclean Synonym for cleandir. + + includes Build and install system header files. Typically needed + before any system libraries or programs can be built. install Install programs, libraries, and documentation into DESTDIR. Few files will be installed to DESTDIR/dev, DESTDIR/etc, @@ -426,11 +482,21 @@ BUILDING installworld Install the distribution from DESTDIR to INSTALLWORLDDIR (which defaults to the root directory). Ensures that - INSTALLWORLDDIR is the not root directory if cross compil- + INSTALLWORLDDIR is not the root directory if cross compil- ing. - Note: It is highly recommended that you upgrade your kernel - and reboot before performing this operation. + The INSTALLSETS environment variable may be set to a list + of distribution sets to be installed. By default, all sets + except ``etc'' and ``xetc'' are installed (so most files in + INSTALLWORLDDIR/etc will not be installed or modified). + + Note: Before performing this operation with + INSTALLWORLDDIR=/, it is highly recommended that you + upgrade your kernel and reboot. After performing this + operation, it is recommended that you use etcupdate(8) to + update files in INSTALLWORLDDIR/etc and that you use + postinstall(8) to check for inconsistencies (and possibly + to fix them). sets Create distribution sets from DESTDIR into RELEASEDIR/MACHINE/binary/sets. Should be run after ``make @@ -440,12 +506,24 @@ BUILDING sourcesets Create source sets of the source tree into RELEASEDIR/source/sets. - release Do a ``make distribution'', build kernels, distribution me- - dia, and install sets (this as per ``make sets''), and then - package the system into a standard release layout as de- - scribed by release(7). This requires that RELEASEDIR be + syspkgs Create syspkgs from DESTDIR into + RELEASEDIR/MACHINE/binary/syspkgs. Should be run after + ``make distribution'' (as ``make build'' does not install + all of the required files). + + release Do a ``make distribution'', build kernels, distribution + media, and install sets (this as per ``make sets''), and + then package the system into a standard release layout as + described by release(7). This requires that RELEASEDIR be set (see above). + iso-image Create a CD-ROM image in + RELEASEDIR/MACHINE/installation/cdrom. RELEASEDIR must + already have been populated by ``make release'' or equiva- + lent. This requires the mkisofs(1) utility, which is not + part of NetBSD, but which can be installed from + pkgsrc/sysutils/cdrtools. + regression-tests Can only be run after building the regression tests in the directory ``regress''. Runs the compiled regression tests @@ -470,8 +548,8 @@ BUILDING The following operations are supported by build.sh: - build Build the system as per ``make build''. This option im- - plies the obj and tools operations. + build Build the system as per ``make build''. This option + implies the obj and tools operations. distribution Build a full distribution as per ``make distribution''. This option implies the build operation. @@ -487,10 +565,11 @@ BUILDING tools Build and install the host tools from src/tools. install=idir Install the contents of DESTDIR to idir, using ``make - installworld''. + installworld''. Note that files that are part of the + ``etc'' or ``xetc'' sets will not be installed. kernel=kconf Build a new kernel. The kconf argument is the name of a - configuration file suitable for use by config(8). If kconf + configuration file suitable for use by config(1). If kconf does not contain any `/' characters, the configuration file is expected to be found in the KERNCONFDIR directory, which is typically sys/arch/MACHINE/conf. The new kernel will be @@ -503,16 +582,19 @@ BUILDING releasekernel=kconf Install a gzip(1)ed copy of the kernel built by kernel=kconf into RELEASEDIR/MACHINE/binary/kernel, usually - as netbsd-kconf.gz, although the ``netbsd'' prefix is de- - termined from the ``config'' directives in kconf. + as netbsd-kconf.gz, although the ``netbsd'' prefix is + determined from the ``config'' directives in kconf. sets Perform ``make sets''. sourcesets Perform ``make sourcesets''. - The following command line options alter the behaviour of the above oper- - ations: The following command line options alter the behaviour of the - build.sh operations described above: + syspkgs Perform ``make syspkgs''. + + iso-image Perform ``make iso-image''. + + The following command line options alter the behaviour of the build.sh + operations described above: -a arch Set the value of MACHINE_ARCH to arch. @@ -522,35 +604,44 @@ BUILDING that the resulting name is of the form ``nbmake-MACHINE-BUILDID''. - -D dest Set the value of DESTDIR to dest. + -D dest Set the value of DESTDIR to dest. If a relative path is speci- + fied, it will be converted to an absolute path before being + used. -E Set `expert' mode. This overrides various sanity checks, and allows: DESTDIR does not have to be set to a non-root path for - builds, and UNPRIVED does not have to be set when building as a - non-root user. + builds, and MKUNPRIVED=yes does not have to be set when build- + ing as a non-root user. Note: It is highly recommended that you know what you are doing when you use this option. + -h Print a help message. + -j njob Passed through to make(1). Makefiles should use .WAIT or have explicit dependancies as necessary to enforce build ordering. If you see build failures with -j, please save complete build logs so the failures can be analyzed. - -M obj Set MAKEOBJDIRPREFIX to obj. - - -m mach Set the value of MACHINE to mach. This will also override any - value of MACHINE_ARCH in the process environment with a value - deduced from mach, unless -a is specified, or mach is a special - case listed below. All cross builds require -m, but if unset - on a NetBSD host, the host's value of MACHINE will be detected - and used automatically. - - Some machines support multiple values for MACHINE_ARCH. For a - given value of mach, the following MACHINE and MACHINE_ARCH - values will result: + -M obj Set MAKEOBJDIRPREFIX to obj. If a relative path is specified, + it will be converted to an absolute path before being used. + Unsets MAKEOBJDIR. + + -m mach Set the value of MACHINE to mach, except in some special cases + listed below. This will also override any value of + MACHINE_ARCH in the process environment with a value deduced + from mach, unless -a is specified. All cross builds require + -m, but if unset on a NetBSD host, the host's value of MACHINE + will be detected and used automatically. + + Some machines support multiple values for MACHINE_ARCH. The + following special cases for the mach argument are defined to + set the listed values of MACHINE and MACHINE_ARCH: mach MACHINE MACHINE_ARCH + evbarm evbarm (not set) + evbarm-eb evbarm armeb + evbarm-el evbarm arm evbmips evbmips (not set) evbmips-eb evbmips mipseb evbmips-el evbmips mipsel @@ -561,41 +652,63 @@ BUILDING sbmips-eb sbmips mipseb sbmips-el sbmips mipsel + -N noiselevel + Set the ``noisyness'' level of the build, by setting + MAKEVERBOSE to noiselevel. + -n Show the commands that would be executed by build.sh, but do not make any changes. This is similar in concept to ``make -n''. -O obj Create an appropriate transform macro for MAKEOBJDIR that will - place the built object files under obj. For instance, a set- - ting of /usr/obj will place build-time files under - /usr/obj/bin, /usr/obj/lib, and so forth. + place the built object files under obj. If a relative path is + specified, it will be converted to an absolute path before + being used. For instance, a setting of /usr/obj will place + build-time files under /usr/obj/bin, /usr/obj/lib, + /usr/obj/usr.bin, and so forth. Unsets MAKEOBJDIRPREFIX. -o Set the value of MKOBJDIRS to ``no''. Otherwise, it will be automatically set to ``yes'' (which is opposite to the default behaviour). - -R rel Set the value of RELEASEDIR to rel. + -R rel Set the value of RELEASEDIR to rel. If a relative path is + specified, it will be converted to an absolute path before + being used. -r Remove the contents of DESTDIR and TOOLDIR before building (provides a clean starting point). This will skip deleting DESTDIR if building on a native system to the root directory. - -T tools Set the value of TOOLDIR to tools. If set, the bootstrap - ``make'' will only be rebuilt as needed (when the source files - for make(1) change). + -T tools Set the value of TOOLDIR to tools. If a relative path is spec- + ified, it will be converted to an absolute path before being + used. If set, the bootstrap ``make'' will only be rebuilt as + needed (when the source files for make(1) change). - -U Set the UNPRIVED variable. + -U Set MKUNPRIVED=yes. - -u Set the UPDATE variable. + -u Set MKUPDATE=yes. -V var=[value] - Set the variable var to value (which is optional). + Set the environment variable var to an optional value. This is + propagated to the nbmake wrapper. -w wrapper Create the nbmake wrapper script (see below) in a custom loca- tion, specified by wrapper. This allows, for instance, to place the wrapper in PATH automatically. Note that wrapper is - the full name of the file, not just a directory name. + the full name of the file, not just a directory name. If a + relative path is specified, it will be converted to an absolute + path before being used. + + -X x11src + Set the value of X11SRCDIR to x11src. If a relative path is + specified, it will be converted to an absolute path before + being used. + + -x Set MKX11=yes. + + -Z var Unset ("zap") the environment variable var. This is propagated + to the nbmake wrapper. The "nbmake-MACHINE" wrapper script If using the build.sh script to build NetBSD, a nbmake-MACHINE script @@ -605,16 +718,19 @@ BUILDING nbmake-MACHINE can be invoked in lieu of make(1), and will instead call the up-to-date version of ``nbmake'' installed into TOOLDIR/bin with sev- eral key variables pre-set, including MACHINE, MACHINE_ARCH, and TOOLDIR. + build.sh will also set variables specified with -V, and unset variables + specified with -Z. + This script can be symlinked into a directory listed in PATH, or called with an absolute path. EXAMPLES - 1. ./build.sh tools kernel=GENERIC + 1. % ./build.sh tools kernel=GENERIC Build a new toolchain, and use the new toolchain to configure and build a new GENERIC kernel. - 2. ./build.sh -U distribution + 2. % ./build.sh -U distribution Using unprivileged mode, build a complete distribution to a DESTDIR directory that build.sh selects (and will display). @@ -626,13 +742,13 @@ EXAMPLES sions stored in DESTDIR/METALOG are correctly applied to the files as they're copied to /. - 4. ./build.sh -U -u release + 4. % ./build.sh -U -u release Using unprivileged mode, build a complete release to DESTDIR and RELEASEDIR directories that build.sh selects (and will display). - UPDATE (-u) is set to prevent the ``make cleandir'', so that if this - is run after example 2, it doesn't need to redo that portion of the - release build. + MKUPDATE=yes (-u) is set to prevent the ``make cleandir'', so that + if this is run after example 2, it doesn't need to redo that portion + of the release build. OBSOLETE VARIABLES NBUILDJOBS Use the make(1) option -j, instead. @@ -642,7 +758,8 @@ OBSOLETE VARIABLES TOOLCHAIN_MISSING=yes. SEE ALSO - make(1), hier(7), release(7) + make(1), hier(7), release(7), etcupdate(8), postinstall(8), + pkgsrc/sysutils/cdrtools HISTORY The build.sh based build scheme was introduced for NetBSD 1.6 as @@ -651,4 +768,4 @@ HISTORY BUGS A few platforms are not yet using this build system. -NetBSD July 3, 2003 NetBSD +NetBSD March 27, 2007 NetBSD