[uClibc]RE: Help: Simple newbie build problem

[James Don]

Ok ... I think I am clear on that now ...

I think I will build my compiler for glibc then get going again from there
... 

Best Regards and thanks for your patience,
Jim


-----Original Message-----
From: Erik Andersen [mailto:andersen at codepoet.org] 
Sent: Tuesday, January 07, 2003 8:55 PM
To: James Don
Cc: uclibc at uclibc.org
Subject: Re: [uClibc]RE: Help: Simple newbie build problem

On Tue Jan 07, 2003 at 08:10:50PM -0500, James Don wrote:
> Sorry guess I should give more detail ... here it goes:
> 
> I just finished getting linux working on a PPC based board with a ram disk
> image from www.denx.de containing bash etc ... to do this I have
built/used
> the following packages:
> 
> 1.) gcc 2.95.3 ... built with newlib
> 2.) ppcboot ... linux bootloader
> 3.) kernel 2.4 form montavista
> 
> Now that I have the kernel running I am moving on to work on writing
> applications ... instead of using an existing development kit ... The
first
> thing I want to build was busybox ... but because my gcc was built with
only
> newlib I think I was running into problems that I otherwise wouldn't have
if
> I used uClibc or glibc ...
> 
> So I decided to build uClibc ... which I have done ...
> 
> Now I am confused by the instructions on "how to build a cross compiler"
at
> (http://penguinppc.org/embedded/cross-compiling/) ... in the example here
> they use glibc ... after compiling the compiler with newlib ... the build
> glibc ... then recompile gcc with glibc ...
> 
> 
> Now my question ... I am now just curious if because I used uClibc I don't
> have to worry about the "recompiling" of gcc with uClibc instead of glibc
> ... I assume the gcc wrappers generated by the uClibc compile lets me skip
> this step.
> 
> I think I have explained ? This is all still new to me ...

Ok, here is the deal.  You have a toolchain.  A toolchain
needs a C library to run.  It also needs a target C library
and header files which it uses when compiling things.

Most people build their toolchains to run on their build systems.
In this configuration, people will typically build their toolchains
linked against glibc, and targeting uClibc.  This is what, for
example, the toolchain builders I relase provide:
    http://uclibc.org/cgi-bin/cvsweb/toolchain/

If you a building a toolchain that you want to have run on a
uClibc-only system, then you want to build your toolchain so it
is linked against uClibc, and also targeting uClibc.  I have an
example of how to build such a thing (make/gcc_target.mk) as part
of buildroot:
    http://uclibc.org/cgi-bin/cvsweb/buildroot/

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--