Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[src/trunk]: src regen using regen target in doc.
details: https://anonhg.NetBSD.org/src/rev/5d9041d2a963
branches: trunk
changeset: 823357:5d9041d2a963
user: wiz <wiz%NetBSD.org@localhost>
date: Thu Apr 20 09:47:52 2017 +0000
description:
regen using regen target in doc.
diffstat:
BUILDING | 458 +++++++++++++++++++++++++++++++-------------------------------
1 files changed, 227 insertions(+), 231 deletions(-)
diffs (truncated from 954 to 300 lines):
diff -r 91e377c0be85 -r 5d9041d2a963 BUILDING
--- a/BUILDING Thu Apr 20 09:47:41 2017 +0000
+++ b/BUILDING Thu Apr 20 09:47:52 2017 +0000
@@ -9,9 +9,9 @@
same NetBSD architecture) or cross compiling (on another architecture or
OS).
- This source tree contains a special subtree, ``tools'', which uses the
- 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
+ This source tree contains a special subtree, "tools", which uses the 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. (See the environment variables section below
if you need to override or manually select your compilers.)
@@ -45,9 +45,9 @@
crypto/dist/, dist/, gnu/dist/
Sources imported verbatim from third parties, without
mangling 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 native host.
+ in bin through usr.sbin use the NetBSD make(1) "reachover"
+ Makefile semantics when building these programs for a
+ native host.
external, sys/external
Sources and build infrastructure for components imported
@@ -68,7 +68,7 @@
sys/ NetBSD kernel sources.
- tools/ ``Reachover'' build structure for the host build tools.
+ tools/ "Reachover" build structure for the host build tools.
This has a special method of determining out-of-date
status.
@@ -78,11 +78,11 @@
during the build.
external/mit/xorg/
- ``Reachover'' build structure for modular Xorg; the source
+ "Reachover" build structure for modular Xorg; the source
is in X11SRCDIR.
- extsrc/ ``Reachover'' build structure for externally added
- programs and libraries; the source is in EXTSRCSRCDIR.
+ extsrc/ "Reachover" build structure for externally added programs
+ and libraries; the source is in EXTSRCSRCDIR.
Build tree layout
The NetBSD build tree is described in hier(7), and the release layout is
@@ -96,14 +96,14 @@
suitable for use during the build. The NetBSD build
system requires a modern Bourne-like shell with POSIX-
compliant features, and also requires support for the
- ``local'' keyword to declare local variables in shell
+ "local" keyword to declare local variables in shell
functions (which is a widely-implemented but non-
standardised feature).
Depending on the host system, a suitable shell may be
/bin/sh, /usr/xpg4/bin/sh, /bin/ksh (provided it is a
- variant of ksh that supports the ``local'' keyword,
- such as ksh88, but not ksh93), or /usr/local/bin/bash.
+ variant of ksh that supports the "local" keyword, such
+ as ksh88, but not ksh93), or /usr/local/bin/bash.
Most parts of the build require HOST_SH to be an
absolute path; however, build.sh allows it to be a
@@ -114,9 +114,9 @@
HOST_CXX Path name to C++ compiler used to create the toolchain.
- MACHINE Machine type, e.g., ``macppc''.
+ MACHINE Machine type, e.g., "macppc".
- MACHINE_ARCH Machine architecture, e.g., ``powerpc''.
+ MACHINE_ARCH Machine architecture, e.g., "powerpc".
MAKE Path name to invoke make(1) as.
@@ -162,7 +162,7 @@
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 printed by
- ``uname -v''.
+ "uname -v".
Default: Unset.
@@ -171,9 +171,9 @@
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).
+ may contain backslash escape sequences, such as "\\"
+ (representing a backslash character) and "\n" (representing a
+ newline).
Default: Unset.
@@ -192,11 +192,10 @@
/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.
+ 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
- otherwise.
+ Default: Empty string if USETOOLS is "yes"; unset otherwise.
Note: build.sh will provide a default of destdir.MACHINE (in
the top-level .OBJDIR) unless run in `expert' mode.
@@ -211,7 +210,7 @@
MAKECONF The name of the make(1) configuration file. Only settable in
the process environment.
- Default: ``/etc/mk.conf''
+ Default: "/etc/mk.conf"
MAKEVERBOSE
Level of verbosity of status messages. Supported values:
@@ -229,149 +228,148 @@
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
+ 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.
+ are traced through use of the sh(1) "-x" flag.
Default: 2
- MKCATPAGES Can be set to ``yes'' or ``no''. Indicates whether
- preformatted plaintext manual pages will be created during a
- build.
+ MKCATPAGES Can be set to "yes" or "no". Indicates whether preformatted
+ plaintext manual pages will be created during a build.
+
+ Default: "no"
- Default: ``no''
+ MKCROSSGDB Can be set to "yes" or "no". Create a cross-gdb as a host
+ tool.
- MKCROSSGDB Can be set to ``yes'' or ``no''. Create a cross-gdb as a
- host tool.
+ Default: "no"
- Default: ``no''
+ MKCRYPTO Can be set to "yes" or "no". Indicates whether cryptographic
+ 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 encryption
+ system, crypt(3).
- MKCRYPTO Can be set to ``yes'' or ``no''. Indicates whether
- cryptographic 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 encryption system, crypt(3).
+ Default: "yes"
- Default: ``yes''
-
- MKDEBUG Can be set to ``yes'' or ``no''. Indicates whether debug
+ MKDEBUG Can be set to "yes" or "no". Indicates whether debug
information should be generated for all userland binaries
compiled. The result is collected as an additional debug.tgz
and xdebug.tgz set and installed in /usr/libdata/debug.
- Default: ``no''
+ Default: "no"
- MKDEBUGLIB Can be set to ``yes'' or ``no''. Indicates whether debug
+ MKDEBUGLIB Can be set to "yes" or "no". Indicates whether debug
information (see MKDEBUG) should also be generated for all
libraries build.
- Default: ``no''
+ Default: "no"
- MKDOC Can be set to ``yes'' or ``no''. Indicates whether system
+ MKDOC Can be set to "yes" or "no". Indicates whether system
documentation destined for DESTDIR/usr/share/doc will be
installed during a build.
- Default: ``yes''
+ Default: "yes"
- MKEXTSRC Can be set to ``yes'' or ``no''. Indicates whether extsrc is
+ MKEXTSRC Can be set to "yes" or "no". Indicates whether extsrc is
built from EXTSRCSRCDIR.
- Default: ``no''
+ Default: "no"
- MKHTML Can be set to ``yes'' or ``no''. Indicates whether
- preformatted HTML manual pages will be built and installed
+ MKHTML Can be set to "yes" or "no". Indicates whether preformatted
+ HTML manual pages will be built and installed
- Default: ``yes''
+ Default: "yes"
- MKHOSTOBJ Can be set to ``yes'' or ``no''. If set to ``yes'', then for
+ MKHOSTOBJ Can be set to "yes" or "no". If set to "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 set to ``no'', then programs
+ "make obj". (This allows multiple host systems to compile
+ NetBSD for a single target.) If set to "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''
+ Default: "no"
- MKINFO Can be set to ``yes'' or ``no''. Indicates whether GNU Info
+ 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 created and installed during a build.
- Default: ``yes''
+ Default: "yes"
- MKKDEBUG Can be set to ``yes'' or ``no''. Force generation of full-
- debug symbol versions of all kernels compiled. Alongside of
- the netbsd kernel file, an unstripped version netbsd.gdb is
+ MKKDEBUG Can be set to "yes" or "no". Force generation of full-debug
+ symbol versions of all kernels compiled. Alongside of the
+ netbsd kernel file, an unstripped version netbsd.gdb is
created. This is useful if a cross-gdb is built as well (see
MKCROSSGDB).
- Default: ``no''
+ Default: "no"
- MKKMOD Can be set to ``yes'' or ``no''. Indicates whether kernel
+ MKKMOD Can be set to "yes" or "no". Indicates whether kernel
modules are built and installed.
- Default: ``yes''
+ 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
+ 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.
- Default: ``yes''
+ Default: "yes"
- MKMAN Can be set to ``yes'' or ``no''. Indicates whether manual
- pages will be installed during a build.
+ MKMAN Can be set to "yes" or "no". Indicates whether manual pages
+ will be installed during a build.
- Default: ``yes''
+ Default: "yes"
- MKNLS Can be set to ``yes'' or ``no''. Indicates whether Native
+ MKNLS Can be set to "yes" or "no". Indicates whether Native
Language System locale zone files will be compiled and
installed during a build.
- Default: ``yes''
+ Default: "yes"
- MKOBJ Can be set to ``yes'' or ``no''. Indicates whether object
- directories will be created when running ``make obj''. If
- set to ``no'', then all built files will be located inside
- the regular source tree.
+ MKOBJ Can be set to "yes" or "no". Indicates whether object
+ directories will be created when running "make obj". If set
+ to "no", then all built files will be located inside the
+ regular source tree.
- Default: ``yes''
+ Default: "yes"
- Note that setting MKOBJ to ``no'' is not recommended and may
+ Note that setting MKOBJ to "no" is not recommended and may
cause problems when updating the tree with cvs(1).
Home |
Main Index |
Thread Index |
Old Index