Cross-compiling toolchain default location choice
ncrfgs
ncrfgs@tin.it
Mon Sep 13 16:08:00 GMT 2004
On Mon, Sep 13, 2004 at 08:27:59AM -0700, Dan Kegel wrote:
> Did you also look at http://kegel.com/crosstool? Ryan is contributing
> improvements to those, too. (He wanted NPTL support, and sent in a patch.
> I'll try to add that in the next release.)
Yes, but I faced some problems when trying to use a custom versions
combo (I'm using a pretty exotic one at the moment) and I needed nptl
support because both CRUX and CRUX PPC (http://cruxppc.sunsite.dk/,
the project I'm developing for) switched to nptl from the 2.0 series.
> I like putting it in /opt/cross/$target/bin/$target-gcc.
Is there a way to make it to coexist with the "regular" toolchain in
/usr?
> I think the 2nd gcc can completely replace the 1st.
Do you think is possible to safely mix libgcc_eh.a and libgcc_s.so*
from the second gcc with the files from the first one?
> But I'm not sure why you care. The full toolchain - gcc and glibc and
> binutils -
> should be a single package built all at once. You should not try to
> mix and match, it's too painful. Crosstool makes a single RPM for all
> components
> of the toolchain.
I'm trying to do so because CRUX generally tries to make different
packages for each single components.
I'm afraid my questions will sound a little bit stupid but I'm new to
the cross compiling world.
Thanks very much for your reply. =)
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
http://www.gnu.org/philosophy/linux-gnu-freedom.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20040913/1992d9cd/attachment.sig>
More information about the crossgcc
mailing list