New issue
Advanced search Search tips

Issue 698328 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

USE="abi_x86_32" does not build/install 32-bit .so files

Project Member Reported by za...@chromium.org, Mar 3 2017

Issue description

To see the problem have BOARD=samus and USE="abi_x86_32"

$ emerge-$BOARD zlib

After running, you can see there is only the 64-bit version:
$ equery-samus f zlib
 * Searching for zlib ...
 * Contents of sys-libs/zlib-1.2.8-r2:
<snip>
/lib64
/lib64/libz.so.1 -> libz.so.1.2.8
/lib64/libz.so.1.2.8
<snip>
/usr/lib64
/usr/lib64/libz.a
/usr/lib64/libz.so
<snip>

I checked to make sure the USE flag was enabled and the package manager claims it was:

$ equery-$BOARD u zlib
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for sys-libs/zlib-1.2.8-r2:
 U I
 - + abi_x86_32  : 32-bit (x86) libraries
 - - minizip     : include the minizip library for quick and dirty zip extraction
 + + static-libs : Build static libraries

 
Labels: OS-Chrome
it depends on the MULTILIB_ABIS setting in the profile.  we use profiles/arch/amd64/no-multilib/make.defaults atm which sets it to just "amd64".

even if we add that though, we still don't have a multilib enabled glibc available.  i'm not sure we're keen on making that available either.

Comment 2 by za...@chromium.org, Mar 6 2017

Sounds like that leaves some prebuilts as my only solution, right?
or build a pure 32-bit/x86 userland
Owner: za...@chromium.org
Status: Assigned (was: Untriaged)
zachr@ what was the resolution

can we close this? 

Comment 5 by vapier@chromium.org, Sep 26 2017

i think we fixed the profile part with the ARC++ multilib work

there's still the question of multilib glibc though which we don't do

Comment 6 by za...@chromium.org, Sep 26 2017

I've just been using prebuilts as my solution. If the USE flag will never be the appropriate solution, I can close this.
Cc: teravest@chromium.org
#6 Where are you getting prebuilts from? I might be down the wrong path while trying to get things working for ARC++ and llvm 4.0, but I hit an error trying to build this package for abi_x86_32 today.

Comment 9 by vapier@chromium.org, Sep 27 2017

this bug doesn't apply to ARC++.  there is multilib support there, so target packages should be building from source and not using prebuilts.
Status: WontFix (was: Assigned)
Closiing this as won't fix.

Sign in to add a comment