Re: glibc vs. newlib in build processes (was:BUG IN DYNAMIC LINKER ld.so)

[Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>]

>Look, I'm not very happy about the state of things either, but I'm not
>ranting about it.  I don't LIKE using newlib when building a linux
>crosscompiler from scratch, but I haven't found an alternative.
>
>What is needed is a way to get target-specific headers out of glibc
>cleanly, without having a crosscompiler installed first.
>
>Since it all appears to be so easy for you, try this: go get a copy of
>a recent Linux disto, say Red Hat 7.1, and install it on a VIRGIN PC.
>No upgrades, wipe the whole thing and start from scratch.  Then give
>me a canned procedure for building powerpc-linux that somehow pulls
>"suitable headers and libraries" out of thin air.  The world will
>thank you.  I will thank you.  CrossGCC will thank you.  Hell, I bet
>even the glibc guys will thank you!

I went through the same saga last month.  I hunted around and found on
the web a procedure to build a cross linux compiler from scratch.  You
*do* have to build the compiler twice, once with newlib, and the
second time with glibc, but with today's CPU's it doesn't take
forever.   I've used it to produce linux cross compilers for ppc and
m68k. 

Try looking at:

http://gfs.lcse.umn.edu/~grant/Linux/cross.html

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

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