| 1 |
Dnia 2013-12-28, o godz. 23:58:39 |
| 2 |
Michał Górny <mgorny@g.o> napisał(a): |
| 3 |
|
| 4 |
> In the multilib stuff, we're using CHOST for two purposes: |
| 5 |
> |
| 6 |
> 1. wrapped headers are put in /usr/include/$CHOST, |
| 7 |
> |
| 8 |
> 2. multilib executables are prefixed with $CHOST-. |
| 9 |
> |
| 10 |
> (...) |
| 11 |
> |
| 12 |
> I'd suggest that you changed the CHOST values to uniquely identify ABI |
| 13 |
> in use, at least in multilib profiles and preferably in all of them. |
| 14 |
|
| 15 |
Ping. The discussion seems stalled while we're hitting increasing |
| 16 |
number of packages that rely on CHOST to run *-config programs. My main |
| 17 |
is that AFAICS this is the only upstream-compatible way of handling |
| 18 |
this without hackery on our side. |
| 19 |
|
| 20 |
As far as I understand, if you changed the CHOSTs only for non-native |
| 21 |
ABIs (and therefore leaving the prefix used for toolchain unchanged) |
| 22 |
the risk should be minimal. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
Archives