All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] classes/base.bbclass: add INCOMPATIBLE_MACHINE
Date: Thu, 08 Jul 2010 13:07:53 -0400	[thread overview]
Message-ID: <20100708170753.GC12383@denix.org> (raw)
In-Reply-To: <1278529036.4413.67.camel@lenovo.internal.reciva.com>

On Wed, Jul 07, 2010 at 07:57:15PM +0100, Phil Blundell wrote:
> On Wed, 2010-07-07 at 20:49 +0200, Frans Meulenbroeks wrote:
> > 2010/7/7 Frans Meulenbroeks <fransmeulenbroeks@gmail.com>:
> > > added INCOMPATIBLE_MACHINE
> > > we have COMPATIBLE_MACHINE but that does not allow to say that
> > > a package is supported by all except a certain machine.
> > > a regexp like "(?!arch)"
> > > This mechanism can be used to exclude certain machines.
> > > Idea is that in binutils and gcc you can use this to specify that
> > > a certain version does not support a certain machine
> > 
> > actually what I wanted to say in the commit message is that a regexp
> > like (?!arch) does not work.
> > \b(?!arch) or ^(?!arch) didn't work either and consulting #python did
> 
> This might just be an accident of wording, but you do realise that
> COMPATIBLE_MACHINE is tested against ${MACHINE} (i.e. not any of the
> ${xx_ARCH} variables), right?  If you want to test arches then you want
> ${COMPATIBLE_ARCH}.
> 
> I just did a quick test with (?!foo) in C_M and it seemed to work ok for
> me.  Specifically:
> 
> MACHINE = goodmach
> COMPATIBLE_MACHINE = "(?!badmach)"
> 
> works, whereas
> 
> MACHINE = badmach
> COMPATIBLE_MACHINE = "(?!badmach)"
> 
> is rejected.  What exactly goes wrong for you?

Just to confirm that the regular expression above does work, when tested 
against the correct variable, as I've been using it for quite a while in my 
recipes, e.g.:

http://arago-project.org/git/?p=arago.git;a=blob;f=recipes/images/arago-qte-image.bb;hb=HEAD

-- 
Denys



      parent reply	other threads:[~2010-07-09 10:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 18:38 [PATCH] classes/base.bbclass: add INCOMPATIBLE_MACHINE Frans Meulenbroeks
2010-07-07 18:49 ` Frans Meulenbroeks
2010-07-07 18:57   ` Phil Blundell
2010-07-07 19:11     ` Frans Meulenbroeks
2010-07-07 19:44       ` Phil Blundell
2010-07-08  6:49         ` Frans Meulenbroeks
2010-07-08  8:23           ` Phil Blundell
2010-07-10 16:19             ` [PATCH] base.bbclass: introduce COMPATIBLE_TARGET_SYS Frans Meulenbroeks
2010-07-10 17:42               ` Tom Rini
2010-07-10 22:36               ` Phil Blundell
2010-07-11  6:55                 ` Frans Meulenbroeks
2010-07-11  7:16                   ` Frans Meulenbroeks
2010-07-11  7:48                     ` [PATCH v2] base.bbclass: introduce COMPATIBLE_TARGET_SYS and COMPATIBLE_TARGET_ARCH Frans Meulenbroeks
2010-07-11  9:10                       ` Phil Blundell
2010-07-11 12:11               ` [PATCH] base.bbclass: introduce COMPATIBLE_TARGET_SYS Phil Blundell
2010-07-12  6:24                 ` Frans Meulenbroeks
2010-07-14  7:27                   ` Esben Haabendal
2010-07-10 16:23             ` [PATCH] classes/base.bbclass: add INCOMPATIBLE_MACHINE Frans Meulenbroeks
2010-07-10 22:52               ` Khem Raj
2010-07-08 17:07     ` Denys Dmytriyenko [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=20100708170753.GC12383@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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.