This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, On Wed, Oct 20, 2010 at 8:11 AM, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote: > All, > > On Wednesday 20 October 2010 08:15:18 Anthony Foiani wrote: >> So it seems that headers for libstdc++ get installed into the sysroot >> (where they are probably not needed), rather than in the cross-compile >> directory itself. > > The issue is that: > - build a cross-toolchain > - use that cross-toolchain to build a full-blown system for your target > - use that cross-toolchain to build a native compiler (same version as in > ?the cross-toolchain) to run on your target (which I call a cross-native, > ?I'm ready to use a better name if you have one) > - you want that compiler to use the same C/C++ headers and libraries as the > ?one from your cross-toolchain, or else you are in trouble. > So you want to be able to copy the sysroot to your target's rootfs and get > all that is needed to build natively on your target. > > I understand "sysroot" as being the "system root" that holds all system > headers and libraries for the target. > the funny thing is that you never intended explicitly, referring to the commit logs and code comments, to put these specific gcc headers in the sysroot. This is a fallout of a change you made back in April. - Arnaud -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |