The site configuration file, `site.exp', captures
configuration-dependent values and propagates them to the DejaGnu test
environment using Tcl variables. This ties the DejaGnu test scripts
DejaGnu supports more than one `site.exp' file. The multiple
instances of `site.exp' are loaded in a fixed order built into
DejaGnu (the more local last). The first file loaded is the optional
~/.dejagnurc, then the local files, and finally the global file.
runtestloads these values first. See section Installing DejaGnu. The master `site.exp' contains the default values for all targets and hosts supported by DejaGnu. This master file is identified by setting the environment variable
DEJAGNUto the name of the file. This is also refered to as the "global" config file.
runtestloads these values last, the individual test configuration can either rely on and use, or override, any of the global values from the "master" `site.exp'. You can usually generate or update the testsuite `site.exp' by typing `make site.exp' in the test suite directory, after the test suite is configured.
.dejagnurc. This gets loaded first before the other config files. Usually this is used for personal stuff, like setting
all_flagso all the output gets printed, or verbosity levels.
You can further override the default values in a user-editable section
of any `site.exp', or by setting variables on the
Go to the first, previous, next, last section, table of contents.