[clc-devel] RFC: Cross-compiling toolchain default location

ncrfgs ncrfgs at tin.it
Sun Sep 19 22:36:38 UTC 2004


After having successfully built a cross-compiling toolchain thanks to
cross-lfs (http://www.linuxfromscratch.org/~ryan/scripts/cross-lfs/),
I'm trying to adapt the wonderful scripts written by Ryan Oliver for
the Linux From Scratch system, to the form of some Pkgbuild package 
building scripts.

Unfortunately while trying to accomplish this task I'm facing some
problems, first of all the choice of the cross-compiling toolchain
default location.

What do you think is the best location in the filesystem for the
cross-compiling toolchain or, in other words, what do you think is
the best configure time prefix to use? At the moment I put it into
/opt/ppc/usr but I wonder whether is there a way to make it to
coexist with the "regular" toolchain in /usr or whether is there a
better location to put it into.

Another problem I'm facing from the package management point of view
are the files that gcc and glibc share among the different build
steps. Maybe it's a bit Off Topic but I hope some of you have some 
experiences to share.

Let's take for example the case of gcc. The gcc-static package shares
all of its files with the gcc-shared package while the following
files are included in the gcc-shared package only.

$PREFIX/powerpc-unknown-linux-gnu/lib/libgcc_s.so -> libgcc_s.so.1

Should gcc-shared be seen as a gcc-static "upgrade"? Or may I safely
delete from the gcc-shared package all the files already installed by
gcc-static and leave only the new ones (namely libgcc_eh.a and

What when, just like in the case of the different glibc builds, the
two packages shares only some files?

Thanks in advance.

Best regards.
Value your freedom, or you will lose it, teaches history. 
``Don't bother us with politics,'' respond those who don't 
want to learn.

 -- Richard M. Stallman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20040920/482e4701/attachment.asc>

More information about the crux-devel mailing list