1 |
On 27/03/14 08:41, Mike Frysinger wrote: |
2 |
> On Thu 27 Mar 2014 02:31:01 Alexandre Rostovtsev wrote: |
3 |
>> On Thu, 2014-03-27 at 02:07 -0400, Mike Frysinger wrote: |
4 |
>>>> An amd64 multilib system *is* expected to build x86 |
5 |
>>>> binaries that would be hosted on itself. So i686-pc-linux-gnu-ar is |
6 |
>>>> expected to be not a part of any cross-compile toolchain, but a part of |
7 |
>>>> the native toolchain for the machine's secondary native ABI. Especially |
8 |
>>>> when i686-pc-linux-gnu-ar is in /usr/bin. |
9 |
>>> sure, and it works just fine when you use the correct toolchain. if the |
10 |
>>> user wants to build an ABI using their default toolchain, they can pass |
11 |
>>> the right ABI flag for it. |
12 |
>> They can't pass the right ABI flag because only the core parts of the |
13 |
>> toolchain have the concept of an ABI flag. |
14 |
>> |
15 |
>> Sure, binutils and gcc respect "-m32". But what about pkgconfig (and its |
16 |
>> clones pkgconf and pkgconfig-openbsd)? What about the *-config tools for |
17 |
>> various libraries? Are you going to patch all of them to respect "-m32"? |
18 |
> pkg-config does need fixing in some way. we already know this. it's why the |
19 |
> multilib eclasses currently set PKG_CONFIG_XXX vars -- preciously so the |
20 |
> correct ABI dir is utilized. and this breaks when using some build systems |
21 |
> (like scons) where the env gets blown away (although we also know scons |
22 |
> sucks). |
23 |
|
24 |
|
25 |
I pushed 0.28-r1 of dev-util/pkgconfig with ABI_X86 support so that you |
26 |
can directly |
27 |
call eg. i686-pc-linux-gnu-pkg-config to search from /usr/lib32/pkgconfig/ |
28 |
|
29 |
I'll try to figure something out for pkgconfig-openbsd too. Don't care |
30 |
about pkgconf. |
31 |
|
32 |
> i don't care about the *-config scripts. that's a dead concept long ago |
33 |
> proven to suck and anything still using it needs fixing. |
34 |
> |
35 |
|
36 |
nod |