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
28 .\" @(#)config.8 8.2 (Berkeley) 4/19/94
35 .Nd build system configuration files
48 utility builds a set of system configuration files from the file
51 the system to configure.
55 what files are needed to generate a system and
56 can be augmented by configuration specific set of files
57 that give alternate files for a specific machine
62 Available options and operands:
63 .Bl -tag -width "SYSTEM_NAME"
69 If the INCLUDE_CONFIG_FILE is present in a configuration file,
70 kernel image will contain full configuration files included
71 literally (preserving comments).
72 This flag is kept for backward compatibility.
76 for any file included by the
79 This option may be specified more than once.
83 as the output directory, instead of the default one.
88 to the directory given.
92 as the source directory, instead of the default one.
94 Print the MACHINE and MACHINE_ARCH values for this
97 Configure a system for debugging.
99 Print kernel configuration file embedded into a kernel
101 This option makes sense only if
102 .Cd "options INCLUDE_CONFIG_FILE"
103 entry was present in your configuration file.
105 Specify the name of the system configuration file
106 containing device specifications, configuration options
107 and other system parameters for one system configuration.
112 utility should be run from the
114 subdirectory of the system source (usually
115 .Pa /sys/ Ns Va ARCH Ns Pa /conf ) ,
118 represents one of the architectures supported by
122 utility creates the directory
123 .Pa ../compile/ Ns Ar SYSTEM_NAME
124 or the one given with the
127 as necessary and places all output files there.
130 consists of a number of files; for the
136 in building the system;
139 the number of various devices that will be compiled into the system.
143 utility looks for kernel sources in the directory
145 or the one given with the
151 it is necessary to run
153 in the directory where the new makefile
157 utility prints a reminder of this when it completes.
159 If any other error messages are produced by
161 the problems in the configuration file should be corrected and
164 Attempts to compile a system that had configuration errors
169 kernels are compiled without symbols due to the heavy load on the
170 system when compiling a
173 A debug kernel contains complete symbols for all the source files, and
174 enables an experienced kernel programmer to analyse the cause of a problem.
176 debuggers available prior to
178 were able to find some information
179 from a normal kernel;
180 .Xr gdb 1 Pq Pa ports/devel/gdb
181 provides very little support for normal kernels, and a debug kernel is needed
182 for any meaningful analysis.
184 For reasons of history, time and space, building a debug kernel is not the
187 a debug kernel takes up to 30% longer to build and
188 requires about 30 MB of disk storage in the build directory, compared to about 6
189 MB for a non-debug kernel.
190 A debug kernel is about 11 MB in size, compared to
191 about 2 MB for a non-debug kernel.
192 This space is used both in the root file
193 system and at run time in memory.
196 option to build a debug kernel.
199 causes two kernel files to be built in the kernel build directory:
203 is the complete debug kernel.
206 is a copy of the kernel with the debug symbols stripped off.
208 to the normal non-debug kernel.
211 There is currently little sense in installing and booting from a debug kernel,
212 since the only tools available which use the symbols do not run on-line.
214 are therefore two options for installing a debug kernel:
217 .Dq Li "make install"
220 in the root file system.
222 .Dq Li "make install.debug"
225 in the root file system.
228 .Bl -tag -width "/sys/ARCH/compile/SYSTEM_NAME" -compact
229 .It Pa /sys/conf/files
230 list of common files system is built from
231 .It Pa /sys/conf/Makefile . Ns Va ARCH
232 generic makefile for the
234 .It Pa /sys/conf/files . Ns Va ARCH
238 .It Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar SYSTEM_NAME
239 default kernel build directory for system
249 portion of each device in section 4.
254 .%T "Building 4.3 BSD UNIX System with Config"
255 .%B 4.4BSD System Manager's Manual (SMM)
266 .Cd "options INCLUDE_CONFIG_FILE"
267 included entire configuration file that used to be embedded in
271 could be used to extract it from a kernel:
272 to extract the configuration information, you had to use
275 .Dl "strings -n 3 kernel | sed -n 's/^___//p'"
277 The line numbers reported in error messages are usually off by one.