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

[bgat at open-widgets dot com]

Y:


Now we're getting somewhere!

I'm so used to always building c/c++ together, I always forget about
the alternative.  I'll give this a whirl.

And like I said, I don't LIKE using newlib headers.  It's clearly a hack.


b.g.

On Wed, Apr 25, 2001 at 09:13:07AM +0100, Yves Rutschle wrote:
> 
> 
> [using newlib headers]
> > 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!
> 
> Well, I did just that for an arm-linux-gcc and I am certain I didn't use
> newlib's headers. I have to agree with Kai here, using another operating
> system's headers makes no sense.
> 
> As you mention, you can't get glibc's target specific headers
> without a cross-compiler already working (which is indeed most
> infortunate, and Kai's idea of having a pre-install would be
> great.. Surely there is no need for a complete compiler to generate
> those headers.) This is why the standard way is to build the
> compiler first, for language C only. For that, you only need
> the configured Linux headers (that you can get with only a native
> compiler -- pfew), and you build the cross-compiler targeting
> linux, without support for the libc (of course, it's not there
> yet). When you have that one, you can compile glibc and get
> your target-specific headers, and rebuild a complete compiler
> if you like (you already are in a state where you can build
> any C application for linux).
> No newlib headers, ever.
> There are details on http://www.armlinux.org/docs/toolchain/
> that describes the procedure for arm-linux, but I don't see
> why it would be any different for other linux targets.
> 
> My 2 pence..  :)
> Y.
> 
> 

-- 
Bill Gatliff
bgat@open-widgets.com

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