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 .\" 4. 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
43 This is the old version of the
46 It understands the old autoconfiguration scheme
47 used on the HP300, i386, DECstation, and derivative platforms.
54 applicable to the architecture that you are running
55 will be installed on your machine.
59 utility builds a set of system configuration files from the file
62 the system to configure.
66 what files are needed to generate a system and
67 can be augmented by configuration specific set of files
68 that give alternate files for a specific machine
73 Available options and operands:
74 .Bl -tag -width ".Ar SYSTEM_NAME"
82 as the output directory, instead of the default one.
87 to the directory given.
89 Configure a system for debugging.
91 Configure a system for profiling; for example,
99 configures a system for high resolution profiling.
101 Specify the name of the system configuration file
102 containing device specifications, configuration options
103 and other system parameters for one system configuration.
108 utility should be run from the
110 subdirectory of the system source (usually
111 .Pa /sys/ Ns Va ARCH Ns Pa /conf ) ,
114 represents one of the architectures supported by
118 utility creates the directory
119 .Pa ../compile/ Ns Ar SYSTEM_NAME
120 or the one given with the
123 as necessary and places all output files there.
126 consists of a number of files; for the
132 in building the system;
135 the number of various devices that will be compiled into the system.
139 it is necessary to run
141 in the directory where the new makefile
145 utility prints a reminder of this when it completes.
147 If any other error messages are produced by
149 the problems in the configuration file should be corrected and
152 Attempts to compile a system that had configuration errors
156 .Cd "options INCLUDE_CONFIG_FILE"
157 is used in the configuration file the
158 entire input file is embedded in the new kernel.
161 can be used to extract it from a kernel:
162 to extract the configuration information, use the command
164 .Dl "strings -n 3 kernel | sed -n 's/^___//p'"
168 kernels are compiled without symbols due to the heavy load on the
169 system when compiling a
172 A debug kernel contains complete symbols for all the source files, and
173 enables an experienced kernel programmer to analyse the cause of a problem.
175 debuggers available prior to
177 were able to find some information
178 from a normal kernel;
180 provides very little support for normal kernels, and a debug kernel is needed
181 for any meaningful analysis.
183 For reasons of history, time and space, building a debug kernel is not the
186 a debug kernel takes up to 30% longer to build and
187 requires about 30 MB of disk storage in the build directory, compared to about 6
188 MB for a non-debug kernel.
189 A debug kernel is about 11 MB in size, compared to
190 about 2 MB for a non-debug kernel.
191 This space is used both in the root file
192 system and at run time in memory.
195 option to build a debug kernel.
198 causes two kernel files to be built in the kernel build directory:
202 is the complete debug kernel.
205 is a copy of the kernel with the debug symbols stripped off.
207 to the normal non-debug kernel.
210 There is currently little sense in installing and booting from a debug kernel,
211 since the only tools available which use the symbols do not run on-line.
213 are therefore two options for installing a debug kernel:
216 .Dq Li "make install"
219 in the root file system.
221 .Dq Li "make install.debug"
224 in the root file system.
227 .Bl -tag -width ".Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar SYSTEM_NAME" -compact
228 .It Pa /sys/conf/files
229 list of common files system is built from
230 .It Pa /sys/conf/Makefile. Ns Va ARCH
231 generic makefile for the
233 .It Pa /sys/conf/files. Ns Va ARCH
237 .It Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar SYSTEM_NAME
238 default kernel build directory for system
248 portion of each device in section 4.
250 .%T "Building 4.3 BSD UNIX System with Config"
258 The line numbers reported in error messages are usually off by one.