This is the mail archive of the
crossgcc@sourceware.org
mailing list for the crossgcc project.
See the CrossGCC FAQ for lots
more information.
Re: [discuss] Problem building cross compiler for x86_64
- From: Kai Ruottu <karuottu at mbnet dot fi>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: 'Mike Frysinger' <vapier at gentoo dot org>, crossgcc at sourceware dot org
- Date: Thu, 19 Jan 2006 18:01:03 +0200
- Subject: Re: [discuss] Problem building cross compiler for x86_64
- References: <SERRANOXiHY5FbEFYam000001f1@SERRANO.CAM.ARTIMI.COM>
Dave Korn wrote:
I'm perfectly happy to do so myself, building a cross-glibc
This sounded a little odd... Why this "cross-" here?
In the very beginning when not understanding much, I produced some kind
of "cross-glibc"'s,
something which would be installed into '$prefix/$target/lib' during the
'make install'... But then
I understood the obvious fact: "If a glibc should be installed into the
native system, it should be
produced for installation into the native system!", someone told here...
So the '--prefix=/usr'
is quite obligatory in the glibc build. And the installation happens
using 'install_root=$sysroot',
with this one gets quite a 1:1 image for the natively installed glibc...
When copying the C library between the cross and native systems, it
doesn't matter whether
the chicken (native) or the egg (cross) system was first, sometimes it
is the chicken, sometimes
it is the egg... But the fact is that something should be in sync
between these and updated on
the other after updating it on the other. The C library is this thing...
So there isn't any 'native glibc' and 'cross glibc', but only 'glibc'
which will be produced for
some '$host', which is the same as '$target' when talking about
libraries. No dependency for
any $host in the GCC build meaning...
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org