[gentoo-user] abi_x86_32

[gentoo-user] abi_x86_32

[Raffaele BELARDI]

I recently switched from no- to multilib. In yesterday's emerge I got
tens of blockers due to conflict with emul-linux-x86-xlibs-20130224.
I solved as suggested in

http://forums.gentoo.org/viewtopic-t-953900.html?sid=f7a643eca8ec01540164578f372c374f

and

http://bugs.gentoo.org/461608

that is by adding abi_x86_32 to USE and unmasking
"emul-linux-x86-xlibs-20130224-r1", but didn't really understand what I
was doing.

Can anybody shed some light on this USE flag and what's going on with
multilib?

thanks,

raffaele

Re: [gentoo-user] abi_x86_32

[Paul Hartman]

On Thu, Mar 28, 2013 at 1:59 AM, Raffaele BELARDI
<raffaele.belardi@st.com> wrote:
> I recently switched from no- to multilib. In yesterday's emerge I got
> tens of blockers due to conflict with emul-linux-x86-xlibs-20130224.
> I solved as suggested in
>
> http://forums.gentoo.org/viewtopic-t-953900.html?sid=f7a643eca8ec01540164578f372c374f
>
> and
>
> http://bugs.gentoo.org/461608
>
> that is by adding abi_x86_32 to USE and unmasking
> "emul-linux-x86-xlibs-20130224-r1", but didn't really understand what I
> was doing.
>
> Can anybody shed some light on this USE flag and what's going on with
> multilib?

Old binary emul-linux* multilib packages are being replaced by a true
compiled-from-source multilib solution. There are a few packages still
need to be updated but it mostly works already. I think it will allow
for more fine-grained dependencies as well for 32-bit apps on 64-bit
systems.

Like the forum post you linked says, instead of setting abi_x86_32 as
a USE flag, what you can do in your make.conf is set:

ABI_X86="64 32"

(if you want to build both 32bit and 64bit)

You may need to unmerge the emul-linux* packages manually then emerge
deep world and figure out if you have any packages that have not yet
been updated to the new way of doing things.

[gentoo-user] Re: abi_x86_32

[Nikos Chantziaras]

On 28/03/13 20:39, Paul Hartman wrote:
> Like the forum post you linked says, instead of setting abi_x86_32 as
> a USE flag, what you can do in your make.conf is set:
>
> ABI_X86="64 32"
>
> (if you want to build both 32bit and 64bit)

I think ABI_X86="32" is enough, since on AMD64 the "64" is always there 
implicitly.

Re: [gentoo-user] Re: abi_x86_32

[Raffaele BELARDI]

On 03/28/2013 08:11 PM, Nikos Chantziaras wrote:
> On 28/03/13 20:39, Paul Hartman wrote:
>> Like the forum post you linked says, instead of setting abi_x86_32 as
>> a USE flag, what you can do in your make.conf is set:
>>
>> ABI_X86="64 32"
>>
>> (if you want to build both 32bit and 64bit)
> 
> I think ABI_X86="32" is enough, since on AMD64 the "64" is always there 
> implicitly.
> 

That was going to be my next question!
By the way, I found this:

$ cat /usr/portage/profiles/desc/abi_x86.desc

# Copyright 2013-2013 Gentoo Foundation.
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/profiles/desc/abi_x86.desc,v 1.2
2013/02/27 23:22:19 mgorny Exp $

# This file contains descriptions of ABI_X86 USE_EXPAND flags.

# Keep it sorted. Please do not add anything without prior discussion
# on gentoo-dev.
32 - 32-bit (x86) libraries
64 - 64-bit (amd64) libraries
x32 - x32 ABI libraries

...and searching for USE_EXPAND in
http://devmanual.gentoo.org/general-concepts/use-flags/ shows that
USE="abi_x86_32" and ABI_X86="32" have the same meaning, which was my
other doubt.

thanks!

[gentoo-user] Re: abi_x86_32

[Nikos Chantziaras]

On 29/03/13 16:21, Raffaele BELARDI wrote:
> By the way, I found this:
>
> $ cat /usr/portage/profiles/desc/abi_x86.desc
>[...]
> 32 - 32-bit (x86) libraries
> 64 - 64-bit (amd64) libraries
> x32 - x32 ABI libraries
>
> ...and searching for USE_EXPAND in
> http://devmanual.gentoo.org/general-concepts/use-flags/ shows that
> USE="abi_x86_32" and ABI_X86="32" have the same meaning, which was my
> other doubt.

It's just a way to provide a default but still be able to override it if 
needed.  Putting ABI_X86="32" in your make.conf will enable abi_x86_32 
for all ebuilds, but you can disable it for individual ebuilds by using 
-abi_x86_32 in package.use.