Getting Started with RTEMS
If you see error messages like the following,
Then it is likely that one or more of your gnu tools is
already configured locally in its source tree. You can check
for this by searching for the config.status file
in the various tool source trees. The following command
does this for the binutils source:
find binutils-2.17 -name config.status -print
The solution for this is to execute the command
make distclean in each of the GNU tools
root source directory. This should remove all
generated files including Makefiles.
This situation usually occurs when you have previously built the tool source for some non-RTEMS target. The generated configuration specific files are still in the source tree and the include path specified during the RTEMS build accidentally picks up the previous configuration. The include path used is something like this:
-I../../binutils-2.17/gcc -I/binutils-2.17/gcc/include -I.
Note that the tool source directory is searched before the build directory.
This situation can be avoided entirely by never using the source tree as the build directory -- even for
Getting Started with RTEMS
Copyright © 1988-2004 OAR Corporation