1 .\" Copyright (c) 1980, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33 .Nd build system configuration files
46 utility builds a set of system configuration files from the file
49 the system to configure.
53 what files are needed to generate a system and
54 can be augmented by configuration specific set of files
55 that give alternate files for a specific machine
60 Available options and operands:
61 .Bl -tag -width "SYSTEM_NAME"
67 If the INCLUDE_CONFIG_FILE is present in a configuration file,
68 kernel image will contain full configuration files included
69 literally (preserving comments).
70 This flag is kept for backward compatibility.
74 for any file included by the
77 This option may be specified more than once.
81 as the output directory, instead of the default one.
86 to the directory given.
90 as the source directory, instead of the default one.
92 Print the MACHINE and MACHINE_ARCH values for this
95 Configure a system for debugging.
97 Print kernel configuration file embedded into a kernel
99 This option makes sense only if
100 .Cd "options INCLUDE_CONFIG_FILE"
101 entry was present in your configuration file.
103 Specify the name of the system configuration file
104 containing device specifications, configuration options
105 and other system parameters for one system configuration.
110 utility should be run from the
112 subdirectory of the system source (usually
113 .Pa /sys/ Ns Va ARCH Ns Pa /conf ) ,
116 represents one of the architectures supported by
120 utility creates the directory
121 .Pa ../compile/ Ns Ar SYSTEM_NAME
122 or the one given with the
125 as necessary and places all output files there.
128 consists of a number of files; for the
134 in building the system;
137 the number of various devices that will be compiled into the system.
141 utility looks for kernel sources in the directory
143 or the one given with the
149 it is necessary to run
151 in the directory where the new makefile
155 utility prints a reminder of this when it completes.
157 If any other error messages are produced by
159 the problems in the configuration file should be corrected and
162 Attempts to compile a system that had configuration errors
167 kernels are compiled without symbols due to the heavy load on the
168 system when compiling a
171 A debug kernel contains complete symbols for all the source files, and
172 enables an experienced kernel programmer to analyse the cause of a problem.
174 debuggers available prior to
176 were able to find some information
177 from a normal kernel;
178 .Xr gdb 1 Pq Pa ports/devel/gdb
179 provides very little support for normal kernels, and a debug kernel is needed
180 for any meaningful analysis.
182 For reasons of history, time and space, building a debug kernel is not the
185 a debug kernel takes up to 30% longer to build and
186 requires about 30 MB of disk storage in the build directory, compared to about 6
187 MB for a non-debug kernel.
188 A debug kernel is about 11 MB in size, compared to
189 about 2 MB for a non-debug kernel.
190 This space is used both in the root file
191 system and at run time in memory.
194 option to build a debug kernel.
197 causes two kernel files to be built in the kernel build directory:
201 is the complete debug kernel.
204 is a copy of the kernel with the debug symbols stripped off.
206 to the normal non-debug kernel.
209 There is currently little sense in installing and booting from a debug kernel,
210 since the only tools available which use the symbols do not run on-line.
212 are therefore two options for installing a debug kernel:
215 .Dq Li "make install"
218 in the root file system.
220 .Dq Li "make install.debug"
223 in the root file system.
226 .Bl -tag -width "/sys/ARCH/compile/SYSTEM_NAME" -compact
227 .It Pa /sys/conf/files
228 list of common files system is built from
229 .It Pa /sys/conf/Makefile . Ns Va ARCH
230 generic makefile for the
232 .It Pa /sys/conf/files . Ns Va ARCH
236 .It Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar SYSTEM_NAME
237 default kernel build directory for system
247 portion of each device in section 4.
252 .%T "Building 4.3 BSD UNIX System with Config"
253 .%B 4.4BSD System Manager's Manual (SMM)
264 .Cd "options INCLUDE_CONFIG_FILE"
265 included entire configuration file that used to be embedded in
269 could be used to extract it from a kernel:
270 to extract the configuration information, you had to use
273 .Dl "strings -n 3 kernel | sed -n 's/^___//p'"
275 The line numbers reported in error messages are usually off by one.