Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] base.bbclass: fix COMPATIBLE_MACHINE
Date: Mon, 11 Apr 2016 09:17:23 +0800	[thread overview]
Message-ID: <570AFB23.9070507@windriver.com> (raw)
In-Reply-To: <20160410190630.GI16135@denix.org>



On 04/11/2016 03:06 AM, Denys Dmytriyenko wrote:
> On Sun, Apr 10, 2016 at 07:14:56AM -0700, Robert Yang wrote:
>> It mismatched such as qemux86 and qemux86-64 which was incorrect, for
>> example:
>> COMPATIBLE_MACHINE = "(qemux86)"
>
> That will match qemux86 and qemux86-64 and is by design! It's a regular

I'm afraid no, please see my last reply, for others such as
MACHINE_OVERRIDES, they never design to work in such a way, so I don't
think that COMPATIBLE_MACHINE should work in this way. If you really
want to match more, I think that you can set it as "(qemux86.*)" or
something familiar.

> expression, not an exact string match! There are plenty of recipes
> (especially outside of oe-core) that depend on this behavior, so please don't
> break it!

I checked oe-core, there isn't any wrong when set MACHINE to:
  "qemuarm"
  "qemuarm64"
  "qemumips"
  "qemumips64"
  "qemuppc"
  "qemux86"
  "qemux86-64"

and run bitbake world -g.

Would you please tell me which recipes outside of oe-core relay on this?
I think that we should fix the recipe.

// Robert

>
>
>> But it treated MACHINE = "qemux86-64" as matched. The similar to others.
>>
>> This patch fixes the problem.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>>   meta/classes/base.bbclass | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
>> index f9697a9..f376478 100644
>> --- a/meta/classes/base.bbclass
>> +++ b/meta/classes/base.bbclass
>> @@ -469,7 +469,7 @@ python () {
>>           import re
>>           compat_machines = (d.getVar('MACHINEOVERRIDES', True) or "").split(":")
>>           for m in compat_machines:
>> -            if re.match(need_machine, m):
>> +            if re.match('^' + need_machine + '$', m):
>>                   break
>>           else:
>>               raise bb.parse.SkipPackage("incompatible with machine %s (not in COMPATIBLE_MACHINE)" % d.getVar('MACHINE', True))
>> --
>> 2.8.0
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>


  reply	other threads:[~2016-04-11  1:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 14:14 [PATCH 0/1] base.bbclass: fix COMPATIBLE_MACHINE Robert Yang
2016-04-10 14:14 ` [PATCH 1/1] " Robert Yang
2016-04-10 17:30   ` Christopher Larson
2016-04-11  1:10     ` Robert Yang
2016-04-10 19:06   ` Denys Dmytriyenko
2016-04-11  1:17     ` Robert Yang [this message]
2016-04-11  1:56       ` Christopher Larson
2016-04-11  2:11         ` Robert Yang
2016-04-11  2:29           ` Denys Dmytriyenko
2016-04-11 13:12             ` Denys Dmytriyenko
2016-04-11  8:29           ` Richard Purdie
2016-04-11  8:33             ` Robert Yang

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=570AFB23.9070507@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=denis@denix.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox