From: Mark Hatle <mark.hatle@windriver.com>
To: jhuang0 <jackie.huang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] multilib.bbclass: Expand the WHITELISTs with multilib prefix
Date: Wed, 28 Aug 2013 13:54:15 -0500 [thread overview]
Message-ID: <521E4757.4080202@windriver.com> (raw)
In-Reply-To: <521C5608.3080508@windriver.com>
On 8/27/13 2:32 AM, jhuang0 wrote:
> Could anyone look at this? It's been a long time here, but no comments
> and is not merged yet.
This is definitely still needed in oe-core. Without this the license
whitelist/blacklist doesn't work as expected when multilibs are enabled.
The only alternative would be to change where the whitelist/blacklist is
evaluated to look for the version w/o the multilib name. But I don't believe
that can be done easily (or perhaps at all.)
--Mark
> Thanks,
> Jackie
>
> On 8/2/2013 5:46 PM, jackie.huang@windriver.com wrote:
>> From: Jackie Huang <jackie.huang@windriver.com>
>>
>> Tested with:
>> require conf/multilib.conf
>> MULTILIBS = "multilib:lib32"
>> DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
>> INCOMPATIBLE_LICENSE = "GPLv3"
>>
>> --
>> The following changes since commit f192c444c2d88c49738bea4ff4c3af0cc72916de:
>>
>> texinfo: Update to 5.1 (2013-07-31 06:56:28 +0100)
>>
>> are available in the git repository at:
>> git://git.pokylinux.org/poky-contrib jhuang0/d_gplv3_0801_2
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jhuang0/d_gplv3_0801_2
>>
>> Jackie Huang (1):
>> multilib.bbclass: Expand the WHITELISTs with multilib prefix
>>
>> meta/classes/multilib.bbclass | 7 +++++++
>> 1 files changed, 7 insertions(+), 0 deletions(-)
>>
>
prev parent reply other threads:[~2013-08-28 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 9:46 [PATCH 0/1] multilib.bbclass: Expand the WHITELISTs with multilib prefix jackie.huang
2013-08-02 9:46 ` [PATCH 1/1] " jackie.huang
2013-08-27 7:32 ` [PATCH 0/1] " jhuang0
2013-08-28 18:54 ` 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=521E4757.4080202@windriver.com \
--to=mark.hatle@windriver.com \
--cc=jackie.huang@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.