Multilibs for arm-elf crossgcc (Part II)

wearpos wearpos@ife.ee.ethz.ch
Sat Jan 26 18:26:00 GMT 2002


Hi

compiling gcc allready succeded but without interworking libs. (only arm and
thumb libs)
So building newlib wouldn't be a problem.

But doing this way i couldn't get newlib to build interworking libs.

So i tried to link the newlib source tree in gcc source tree.
I had some postings on newlib mailinglist and were told to do so. They told
me that makeing multilibs from newlibs is done under control of gcc.

But as you analyse the problem i think it would help first building gcc
without c++ (so newlib will build as interwork), installing it and then
recompile gcc incl. c++.
What do you think about this? The only way?

Thanks

Alex


>
> My guess is that the configure of libstdc++-v3 failed because you haven't
> got newlib installed yet.
>
> Do you have a unified tree? or separate gcc and newlib trees.
>
> Assuming the latter (most common case), then what you need to do when
> building the compiler is
>
> cd [gcc-build]
> .../configure --target=arm-elf ...
> gnumake all-gcc
> gnumake install-gcc
> cd [newlib-build]
> .../configure --target=arm-elf ...
> gnumake all-newlib
> gnumake install-newlib
> cd [gcc-build]
> gnumake all
> gnumake install
>
> Sounds a bit convoluted but you can't build newlib until you have a
> comiler, and you can't build the compiler libraries until you have
> newlib...
>
> R.
>
>
>
> ------
> Want more information?  See the CrossGCC FAQ,
http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to
crossgcc-unsubscribe@sources.redhat.com
>


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com



More information about the crossgcc mailing list