| 1 |
On Thu, 2014-03-27 at 02:07 -0400, Mike Frysinger wrote: |
| 2 |
> > An amd64 multilib system *is* expected to build x86 |
| 3 |
> > binaries that would be hosted on itself. So i686-pc-linux-gnu-ar is |
| 4 |
> > expected to be not a part of any cross-compile toolchain, but a part of |
| 5 |
> > the native toolchain for the machine's secondary native ABI. Especially |
| 6 |
> > when i686-pc-linux-gnu-ar is in /usr/bin. |
| 7 |
> |
| 8 |
> sure, and it works just fine when you use the correct toolchain. if the user |
| 9 |
> wants to build an ABI using their default toolchain, they can pass the right |
| 10 |
> ABI flag for it. |
| 11 |
|
| 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"? |
Archives