| 1 |
On Tue, 27 Dec 2016 12:04:04 -0500 |
| 2 |
Mike Gilbert <floppym@g.o> wrote: |
| 3 |
|
| 4 |
> For a typical cross-compiler build, CHOST is unchanged from the value |
| 5 |
> typically in make.conf, but CTARGET gets set to the "cross" arch. |
| 6 |
|
| 7 |
Yep. |
| 8 |
|
| 9 |
> In the case where we are cross-compiling a native compiler, CHOST |
| 10 |
> would be taken from ${ROOT}/etc/portage/make.conf, and ROOT would |
| 11 |
> typically be something like /usr/${cross_arch}/. So I think we are |
| 12 |
> safe there as well. |
| 13 |
|
| 14 |
I seem to recall installing a native compiler to /usr/${cross_arch}/ |
| 15 |
resulted in file conflicts but if that's still the case, that's a |
| 16 |
separate issue. ROOT may possibly need to change to SYSROOT but that's |
| 17 |
also a separate issue. |
| 18 |
|
| 19 |
> What I'm very unsure of is cross-compiling a cross-compiler CBUILD != |
| 20 |
> CHOST != CTARGET. That requires a bit of thought. I'm not sure we even |
| 21 |
> really support that in toolchain.eclass though. |
| 22 |
|
| 23 |
This is called a Canadian cross. I can't remember if I ever actually |
| 24 |
tried one but I think your change would still be correct in this case. |
| 25 |
We don't care about CBUILD in this context. |
| 26 |
|
| 27 |
-- |
| 28 |
James Le Cuirot (chewi) |
| 29 |
Gentoo Linux Developer |
Archives