f78
Error
messages and warnings that may display
The following documentation
discusses the warnings or error messages that may display during your build
process. With each message, a troubleshooting approach accompanies for
resolution.
% set path=/usr/gnupro/bin/ $pathname % setenv CC /usr/gnupro/bin/gcc % configure ... % make
% PATH=/usr/gnupro/bin:$ pathname % CC=/usr/gnupro/bin/gcc % export PATH CC % configure ... % makeIf you still experience configuration problems, first try to rerun configure by adding the command line option, --verbose. It’s best to redirect the output to a log file while running this process.
% configure -–verbose ... >& configure.out
% configure -–verbose ... >configure.out 2>&1Some seemingly unrelated problems arise after applying patches or making other changes. For instance, sometimes file dependencies get confused. With any trouble you have building, an easy step to take is to remove your build directory completely and then rebuild in an empty build direrctory, using the following example’s input.
% rm -rf /usr/cygnus/release_name/build
% mkdir /usr/cygnus/release_name/build
For more information on installing GNUPro Toolkit, see Installation in Getting Started with GNUPro Toolkit.
If it’s not obvious which part of the toolkit is failing, check the last line in the log that begins “Configuring...” such as, with the debugging tool, gdb, you’d see “Configuring gdb...” before configure stops.
configure also creates a config.log file in each sub-directory in which it runs tests. Check the end of the config.log where it failed for specific information about what went wrong. The last page (25-30 lines) of this file should be plenty, but if in doubt, send the entire file. See Contacting Cygnus. 0