[uClibc] [buildroot] toolchain usage & file hierarchy

Flavio Castelli micron at madlab.it
Wed Aug 24 10:51:07 UTC 2005


Here's my situation: I need to build some programs for a mipsel target 
machine, using a powerpc (or x86) as host .
The mipsel target is a linux box router so I can't compile anything natively. 
So I decided to create a mipsel toolchain using buildroot.

After using buildroot I've obtained a working toolchain that produces mipsel 
binaries starting from my powerpc machine.

But the main problem is the toolchain's file hierarchy, which is (IMHO) quite 
"obscure" and little pratical.

It's obscure because there're multiple directories for the same thing, for 
example I have:
-) under buildroot dir: toolchain and toolchain_build_mipsel
-) under toolchain_build_mipsel dir: binutils-2.16.1 and 
binutils-2.16.1-build, gcc-3.3.5 and gcc-3.3.5-initial and 
gcc-3.3.5-final, ...

I understand that these duplicates directories are needed for the canadian 
build, but I think that would be more useful to collect all cross-bins.
IMHO it would be more pratical to have them (gcc-croos, strip-new,...) 
organized under a new user defined dir (like /opt/toolchain_build_mipsel/) as 
is make by croosstool.

I'm telling these things because it's difficult to find some cross-bin 
(finding cross-gcc took me some minutes) and is more difficult to keep 
updated the Makefiles (if I upgrade to gcc-3.4 I've to change gcc-croos path 
in all makefiles or do some other dirty tricks).

Obviously this's only a possible solution for my problem, other 
solutions/hints are accepted.

Thanks a lot
	Flavio
-- 
|§ micron<- ICQ #118796665
|§ GPG Key:
|§  ~ Keyserver: pgp.mit.edu
|§  ~ KeyID: 6D632BED

~ "Progress is merely a realisation of utopias" ~



More information about the uClibc mailing list