| 1 |
On 19 Jan 2016 13:47, Alex McWhirter wrote: |
| 2 |
> In many places im seeing LD output this in the configure script of a |
| 3 |
> multilib glibc ebuild. This is configuring 32bit glibc on a 64bit host. |
| 4 |
> |
| 5 |
> sparc:v9 architecture of input file `somefile' is incompatible with |
| 6 |
> sparc output |
| 7 |
> |
| 8 |
> So it looks like LD is working right, but GCC is still compiling 64bit. |
| 9 |
> Or it could be G++ compiling 64bit as i don't see a -m32 flag set for |
| 10 |
> it? I seem some references to G++. |
| 11 |
|
| 12 |
i'm guessing the multilib toolchain setup isn't working correctly. |
| 13 |
can you attach the full log ? |
| 14 |
|
| 15 |
what should be happening: |
| 16 |
- profile declares CFLAGS_sparc32 and friends for correct ABI settings |
| 17 |
- profile declares the active list of ABIs |
| 18 |
- `portageq envvar MULTILIB_ABIS` should return "sparc64 sparc32" |
| 19 |
- glibc ebuild uses multilib.eclass to set up the toolchain |
| 20 |
- uses profile env var settings |
| 21 |
- see multilib_toolchain_setup and multilib_env |
| 22 |
- ebuild log the exact settings used before configure to check |
| 23 |
- those settings are passed down to configure invocation |
| 24 |
|
| 25 |
wrt g++, we might not be setting up CXXFLAGS in the glibc ebuild as this |
| 26 |
hasn't historically come up. |
| 27 |
-mike |
Archives