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. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)config.8 8.2 (Berkeley) 4/19/94
40 .Nd build system configuration files
47 This is the old version of the
50 It understands the old autoconfiguration scheme
51 used on the HP300, i386, DECstation, and derivative platforms.
58 applicable to the architecture that you are running
59 will be installed on your machine.
62 builds a set of system configuration files from the file
65 the system to configure.
69 what files are needed to generate a system and
70 can be augmented by configuration specific set of files
71 that give alternate files for a specific machine
76 Available options and operands:
77 .Bl -tag -width ".Ar SYSTEM_NAME"
81 as the output directory, instead of the default one.
86 to the directory given.
88 Configure a system for debugging.
90 Configure a system for profiling; for example,
98 configures a system for high resolution profiling.
100 Specify the name of the system configuration file
101 containing device specifications, configuration options
102 and other system parameters for one system configuration.
106 should be run from the
108 subdirectory of the system source (usually
109 .Pa /sys/ Ns Va ARCH Ns Pa /conf ) ,
112 represents one of the architectures supported by
115 creates the directory
116 .Pa ../compile/ Ns Ar SYSTEM_NAME
117 or the one given with the
120 as necessary and places all output files there.
123 consists of a number of files; for the
128 of what I/O devices are attached to the system;
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
144 prints a reminder of this when it completes.
146 If any other error messages are produced by
148 the problems in the configuration file should be corrected and
151 Attempts to compile a system that had configuration errors
155 .Cd "options INCLUDE_CONFIG_FILE"
156 is used in the configuration file the
157 entire input file is embedded in the new kernel.
160 can be used to extract it from a kernel:
161 to extract the configuration information, use the command
163 .Dl "strings kernel | grep ___"
167 kernels 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;
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 ".Pa /sys/ Ns Va ARCH Ns Pa /compile/ Ns Ar 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
245 portion of each device in section 4.
247 .%T "Building 4.3 BSD UNIX System with Config"
250 The line numbers reported in error messages are usually off by one.