Tutorial 3

[Phil Edwards]

On Sun, Jun 16, 2002 at 06:40:42PM -0400, Mark Butcher wrote:
> checking how to run the C preprocessor... (cached) /lib/cpp

That's never a good sign.

For some history of why this happens, and what's causing it, take a look
at the messages in libstdc++/2255:

    http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2255&database=gcc

It isn't a libstdc++ problem, obviously, since you're seeing it far before
the build even gets to libstdc++, but that's the PR that I had in my notes.

There's some further discussion from that PR in the mail archives:

    http://gcc.gnu.org/ml/libstdc++/2001-05/msg00009.html


> checking whether the C compiler (/usr/local/src/gnu/BUILD/gcc/gcc/xgcc
> -B/usr/local/src/gnu/BUILD/gcc/gcc/ -B/usr/local/mcore/mcore-elf/bin/
> -B/usr/local/mcore/mcore-elf/lib/ -isystem
> /usr/local/mcore/mcore-elf/include -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
> make: *** [configure-target-libiberty] Error 1
> 
> [The error is because the linker doesn't find "crt0.o"]

Yep.  This kind of error is what causes everything else to die and results
in weird settings like the /lib/cpp thing about.  It's almost always related
to not finding the standard C library headers or the system startup files,
which are (again, almost always) the two most common symptoms of the same
problem:  the cross-compiler hasn't properly been told where to find the
C library stuff to use.

Does that help at all?


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams