Contents|Index|Previous|Next

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.

Make: Fatal error: Don’t know how to make target ‘foo.c’
Make sure, first, of course, that you are using GNU make.You could be using a make that isn’t configured. make will accept the --version option, for telling you that you are using GNU make as well as which version you are running; if you have this error message, try running the command, make –version.

Incorrect compiler used.
When configure runs, it looks for an appropriate compiler, first gcc, then cc. If neither of these is correct, specify the name of the compiler at configuration time. We recommend that you always build with gcc.The best way to determine configure can find it correctly is to ensure that it is in your path ahead of other compilers. Specify the compiler by setting the $CC environment variable before running configure. In the following example, the correct compiler is /usr/progressive/bin/gcc.

- If you are using C shell, use a command similar to the following example’s input where pathname is the path you require.

    % set path=/usr/progressive/bin/ $pathname
    % setenv CC /usr/progressive/bin/gcc
    % configure ...
    % make

- In Bourne shell (/bin/sh) or Korn shell, use the following example’s input.

    % PATH=/usr/progressive/bin:$ pathname
    % CC=/usr/progressive/bin/gcc
    % export PATH CC
    % configure ...
    % make

If 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.

- If you are using C shell, use a command similar to the following example’s input.

    % configure -–verbose ... >& configure.out

- With Bourne shell, use the following example’s input.

    % configure -–verbose ... >configure.out 2>&1

Some 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 and “Overview of Release Notes for GNUPro Toolkit” in Release Notes for 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 Solutions.