From: Raffaele BELARDI <raffaele.belardi@st.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: abi_x86_32
Date: Fri, 29 Mar 2013 15:21:44 +0100 [thread overview]
Message-ID: <5155A378.2040102@st.com> (raw)
In-Reply-To: <kj24lk$goo$1@ger.gmane.org>
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!
next prev parent reply other threads:[~2013-03-29 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 6:59 [gentoo-user] abi_x86_32 Raffaele BELARDI
2013-03-28 18:39 ` Paul Hartman
2013-03-28 19:11 ` [gentoo-user] abi_x86_32 Nikos Chantziaras
2013-03-29 14:21 ` Raffaele BELARDI [this message]
2013-03-30 6:20 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5155A378.2040102@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox