From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] local.conf.sample.extended: update for preferred ABI
Date: Thu, 31 Jul 2014 08:55:23 -0500 [thread overview]
Message-ID: <53DA4ACB.2070902@windriver.com> (raw)
In-Reply-To: <1406814326.13346.179.camel@ted>
On 7/31/14, 8:45 AM, Richard Purdie wrote:
> On Thu, 2014-07-31 at 16:18 +0800, Robert Yang wrote:
>>
>> On 07/31/2014 04:15 PM, Robert Yang wrote:
>>> [YOCTO #4073]
>>>
>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>> ---
>>> meta/conf/local.conf.sample.extended | 15 +++++++++++++++
>>> 1 file changed, 15 insertions(+)
>>>
>>> diff --git a/meta/conf/local.conf.sample.extended b/meta/conf/local.conf.sample.extended
>>> index 89b80a6..8ad7b6f 100644
>>> --- a/meta/conf/local.conf.sample.extended
>>> +++ b/meta/conf/local.conf.sample.extended
>>> @@ -145,6 +145,13 @@
>>> #MULTILIBS = "multilib:lib32"
>>> #DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>>>
>>> +# Set RPM_PREFER_COLOR to configure preferred ABI when using rpm packaging
>>> +# backend to generate a rootfs, choices are:
>>> +# 1: ELF32 wins
>>> +# 2: ELF64 wins
>>> +# 3: ELF64 N32 wins (for mips64 or mips64el only)
>>> +#RPM_PREFER_COLOR ?= "2"
>>> +
>
> Is x86 x32 also color 3?
x32 support was never implemented. RPM has no unique identification for x32
binaries at this time. They're treated as ELF64 if I remember correctly.
If implemented, I would expect it to piggy back on '3' as well.
--Mark
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2014-07-31 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 8:15 [PATCH 0/2] package_manager.py: set preferred ABI for rpm Robert Yang
2014-07-31 8:15 ` [PATCH 1/2] " Robert Yang
2014-07-31 8:15 ` [PATCH 2/2] local.conf.sample.extended: update for preferred ABI Robert Yang
2014-07-31 8:18 ` Robert Yang
2014-07-31 13:45 ` Richard Purdie
2014-07-31 13:55 ` Mark Hatle [this message]
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=53DA4ACB.2070902@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.