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