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
36 .Nd build system configuration files
49 utility builds a set of system configuration files from the file
52 the system to configure.
56 what files are needed to generate a system and
57 can be augmented by configuration specific set of files
58 that give alternate files for a specific machine
63 Available options and operands:
64 .Bl -tag -width "SYSTEM_NAME"
70 If the INCLUDE_CONFIG_FILE is present in a configuration file,
71 kernel image will contain full configuration files included
72 literally (preserving comments).
73 This flag is kept for backward compatibility.
77 for any file included by the
80 This option may be specified more than once.
84 as the output directory, instead of the default one.
89 to the directory given.
93 as the source directory, instead of the default one.
95 Print the MACHINE and MACHINE_ARCH values for this
98 Configure a system for debugging.
100 Print kernel configuration file embedded into a kernel
102 This option makes sense only if
103 .Cd "options INCLUDE_CONFIG_FILE"
104 entry was present in your configuration file.
106 Specify the name of the system configuration file
107 containing device specifications, configuration options
108 and other system parameters for one system configuration.
113 utility should be run from the
115 subdirectory of the system source (usually
116 .Pa /sys/ Ns Va ARCH Ns Pa /conf ) ,
119 represents one of the architectures supported by
123 utility creates the directory
124 .Pa ../compile/ Ns Ar SYSTEM_NAME
125 or the one given with the
128 as necessary and places all output files there.
131 consists of a number of files; for the
137 in building the system;
140 the number of various devices that will be compiled into the system.
144 utility looks for kernel sources in the directory
146 or the one given with the
152 it is necessary to run
154 in the directory where the new makefile
158 utility prints a reminder of this when it completes.
160 If any other error messages are produced by
162 the problems in the configuration file should be corrected and
165 Attempts to compile a system that had configuration errors
170 kernels are compiled without symbols due to the heavy load on the
171 system when compiling a
174 A debug kernel contains complete symbols for all the source files, and
175 enables an experienced kernel programmer to analyse the cause of a problem.
177 debuggers available prior to
179 were able to find some information
180 from a normal kernel;
182 provides very little support for normal kernels, and a debug kernel is needed
183 for any meaningful analysis.
185 For reasons of history, time and space, building a debug kernel is not the
188 a debug kernel takes up to 30% longer to build and
189 requires about 30 MB of disk storage in the build directory, compared to about 6
190 MB for a non-debug kernel.
191 A debug kernel is about 11 MB in size, compared to
192 about 2 MB for a non-debug kernel.
193 This space is used both in the root file
194 system and at run time in memory.
197 option to build a debug kernel.
200 causes two kernel files to be built in the kernel build directory:
204 is the complete debug kernel.
207 is a copy of the kernel with the debug symbols stripped off.
209 to the normal non-debug kernel.
212 There is currently little sense in installing and booting from a debug kernel,
213 since the only tools available which use the symbols do not run on-line.
215 are therefore two options for installing a debug kernel:
218 .Dq Li "make install"
221 in the root file system.
223 .Dq Li "make install.debug"
226 in the root file system.
229 .Bl -tag -width "/sys/ARCH/compile/SYSTEM_NAME" -compact
230 .It Pa /sys/conf/files
231 list of common files system is built from
232 .It Pa /sys/conf/Makefile . Ns Va ARCH
233 generic makefile for the
235 .It Pa /sys/conf/files . Ns Va ARCH
239 .It Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar SYSTEM_NAME
240 default kernel build directory for system
250 portion of each device in section 4.
255 .%T "Building 4.3 BSD UNIX System with Config"
256 .%B 4.4BSD System Manager's Manual (SMM)
267 .Cd "options INCLUDE_CONFIG_FILE"
268 included entire configuration file that used to be embedded in
272 could be used to extract it from a kernel:
273 to extract the configuration information, you had to use
276 .Dl "strings -n 3 kernel | sed -n 's/^___//p'"
278 The line numbers reported in error messages are usually off by one.