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.41 retrieving revision 1.55 diff -u -p -r1.41 -r1.55 --- src/BUILDING 2003/08/08 01:52:24 1.41 +++ src/BUILDING 2006/01/12 21:22:30 1.55 @@ -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,10 @@ CONFIGURATION Environment variables Several environment variables control the behaviour of NetBSD builds. + 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. @@ -141,6 +148,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 +168,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 +209,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 +231,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,28 +245,39 @@ 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'' - MKUNPRIVED Can be set to ``yes'' or ``no''. Indicates whether an un- - privileged install will occur. The user, group, permissions, - and file flags, will not be set on the installed item; in- - stead 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. + 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: ``no'' + + 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: ``no'' - MKUPDATE Can be set to ``yes'' or ``no''. Indicates whether all in- - stall operations intended to write to DESTDIR will compare + 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 im- - plications on full builds (see next subsection). + 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'' @@ -280,8 +310,13 @@ 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. 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 @@ -292,8 +327,8 @@ CONFIGURATION 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'' @@ -327,8 +362,8 @@ 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 MKUPDATE=yes in that case. @@ -345,12 +380,12 @@ CONFIGURATION 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. @@ -364,7 +399,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- @@ -381,14 +416,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. @@ -396,8 +429,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, @@ -430,7 +465,7 @@ 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 @@ -444,10 +479,15 @@ 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). regression-tests @@ -474,8 +514,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. @@ -494,7 +534,7 @@ BUILDING installworld''. 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 @@ -507,16 +547,17 @@ 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''. + + 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. @@ -536,6 +577,8 @@ BUILDING 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 @@ -565,6 +608,10 @@ 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''. @@ -603,6 +650,11 @@ BUILDING place the wrapper in PATH automatically. Note that wrapper is the full name of the file, not just a directory name. + -X x11src + Set the value of X11SRCDIR to x11src. + + -x Set MKX11=yes. + -Z var Unset ("zap") the environment variable var. This is propagated to the nbmake wrapper. @@ -621,12 +673,12 @@ BUILDING 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). @@ -638,7 +690,7 @@ 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). @@ -663,4 +715,4 @@ HISTORY BUGS A few platforms are not yet using this build system. -NetBSD August 7, 2003 NetBSD +NetBSD January 4, 2006 NetBSD