1 |
On Saturday 01 September 2007, Peter Stuge wrote: |
2 |
> On Thu, Aug 30, 2007 at 06:03:58PM -0400, Mike Frysinger wrote: |
3 |
> > is_crosscompile is used to detect whether we're building a |
4 |
> > cross-compiler, not whether we're cross-compiling the compiler |
5 |
> |
6 |
> Suggest name change to is_crosscompiler |
7 |
|
8 |
makes sense |
9 |
|
10 |
> > > The point is though, that even for straight cross-compiles it's |
11 |
> > > usually more dependent on CHOST being set to a different |
12 |
> > > architecture than CTARGET. |
13 |
> > |
14 |
> > in the normal case, CTARGET is never set ... however, for all |
15 |
> > toolchain based packages, the three tuples (CBUILD CHOST CTARGET) |
16 |
> > are made sure to be set to the correct value |
17 |
> |
18 |
> What about those --enable-serial-* though? Is there a better |
19 |
> solution for the author's problem? |
20 |
|
21 |
i really dont have an idea of what the problem is. i build cross-compilers |
22 |
and cross-compile native compilers and cross-compile cross-compilers and have |
23 |
yet to hit any problems (which are not fixed in the current tree). |
24 |
-mike |