Re: Resulting toolchain for MIPS

[Dan Kegel <dank at kegel dot com>]

Thomas Petazzoni wrote:
> I suscessfully compiled a toolchain for MIPS big endian with gcc 3.4.1
> and glibc 2.3.2, kernel 2.6.8.1. The statically-linked simple "Hello
> World" program works (either using MIPS-I instruction set or MIPS-II
> instruction set). I used crosstools-0.28-rc35 by Dan Kegel.
>
> There is only one thing I don't understand clearly : the organization of
> the resulting toolchain.
>
> In mips-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.2/, I have :
>
>  * A bin/ directory which contains binairies like
>  mips-unknown-linux-gnu-gcc.
>
>  * A mips-unknown-linux-gnu directory which itself contains a bin/
>    directory which contains binaries like gcc, ld, ar ... These binaries
>    are the same as the one present in mips-unknown-linux-gnu (same MD5).
> So
>    why are they present with another name at an other place ?
>
> More generally, what is this mips-unknown-linux-gnu directory ? It seems
> important because if I delete it, I can't compile a program anymore
> because glibc headers aren't present.

Here's a handwavy explanation you probably already guessed:
The bin directory is the one with the long names ($target-gcc).
The $target/bin directory is the one with the short names (gcc).
I seem to recall gcc internally uses the short-named executables when
invoking subprograms.
So you need 'em both.
And the $target directory is where other target-specific stuff,
like internal headers and libraries, are stored, too.

Are you short on disk space?  Not sure why else you'd want to delete
parts of the toolchain...
- Dan

--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

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