Re: [Fwd: conflicting type for syserr_list]

[Jeffrey A Law <law at cygnus dot com>]

  In message <35BF16EF.ACF82987@kieray1.p.y.ki.era.ericsson.se>you write:
  > Yes it gives the same problem. But how is this ever going to work ?? I mean
:-)  Welcome to the world of cross compilation, nothing is easy here.


The way we usually make this work is with the following sequence:

Build host tools like flex, bison, etc.
Build target tools needed by the target compiler (gas, ld, nm, etc).
Build the target compiler.
Build the target libraries, starting with newlib, then progressing
to libiberty/libstdc++

gdb can pretty much be built anytime after the host tools are done.

The "one tree build" environment handles this stuff automatically.

Note that you're not using newlib, but instead you're using glibc.


  > The question then is why do I need system header files and
  > libraries to build the cross compiler
You're getting the failure while building runtime libraries for the
target, not while building the compiler itself.  Unlike gcc2, we
include certain runtime libraries in our distributions.  The cross-gcc
faq is not 100% up to date I suspect.

jeff