Installation guide

Definition Time Invoked
at_start
After the config command has parsed the
configuration file syntax but before processing any input
at_exit
Immediately before the config command exits,
regardless of its exit status
at_success
Before the at_exit process, if specified, and only if the
config command exits with a success exit status
before_h
Before the config command creates any *.h files
after_h
After the config command creates any *.h files
before_c
Before the config command creates any *.c files
after_c
After the config command creates any *.c files
before_makefile
Before the config command creates the Makefile file
after_makefile
After the config command creates the Makefile file
before_conf
Before the config command creates the conf.c file
after_conf
After the config command creates the conf.c file
More than one callout keyword with the same parameter can be in the
configuration file, and the subprocesses are invoked in the order that they
appear in the file. The following is an example of some configuration file
entries:
callout at_exit "echo Exit 1 | mail root"
callout at_exit "echo Exit 2 | mail root"
callout at_success "echo Configuration successful | mail root"
If the config command exits successfully, the sequence of the information
mailed to root is as follows:
1. Configuration successful
2. Exit 1
3. Exit 2
5.6.5 The options Keyword Definitions
The configuration file contains several definitions that are preceded by the
options keyword. In general, these definitions specify the components
that define the kernel itself, the subsystems, and additional functionality
that is required for the target system to operate correctly. These
dependency options usually are mandatory and should not be removed from
the configuration file or altered. See Table 5–2 for a complete list of
dependency options.
Configuring the Kernel 5–49