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] | |
On Sun, 2007-05-06 at 17:07 +0100, Dave Korn wrote: > On 06 May 2007 17:03, Jonathan S. Shapiro wrote: > > > On Sun, 2007-05-06 at 16:38 +0100, Dave Korn wrote: > >>> Simply knowing the architecture isn't enough, because you have no way to > >>> know where the headers live in my tree (well, for my tree you might, but > >>> not in general). > >> > >> They live in $prefix/include. Don't see what the problem is. What is > >> "your" tree? We're building a *cross*-compiler here. > > > > "My" tree is the source tree for the operating system that we are > > attempting to build the cross tools here. > > Then they live in the source tree's include dir, and you point the build > process at it by providing either --with-sysroot or --with-headers. Dave: >From experience, this doesn't work. We are committed to using --with-sysroot for other reasons, and --with-headers is (allegedly) incompatible with --with-sysroot. What we need to do in our case is put a temporary copy of the system headers somewhere in the cross-tools build tree. shap -- 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] |