From: Patrick Ohly <patrick.ohly@intel.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] native.bbclass: clear MACHINE_FEATURES
Date: Thu, 23 Mar 2017 20:09:03 +0100 [thread overview]
Message-ID: <1490296143.6396.253.camel@intel.com> (raw)
In-Reply-To: <CAJ86T=USCOn32KPsH1TURbJL671wPwGXLBeajkL06wyvs4Q0wA@mail.gmail.com>
On Thu, 2017-03-23 at 11:59 -0700, Andre McCurdy wrote:
> On Thu, Mar 23, 2017 at 2:06 AM, Mike Looijmans <mike.looijmans@topic.nl> wrote:
> > On 22-03-17 23:47, Andre McCurdy wrote:
> >>
> >> Try to avoid native recipes accidentally being dependent on
> >> MACHINE_FEATURES. This simple change doesn't prevent MACHINE_FEATURES
> >> set via MACHINE_FEATURES_BACKFILL sneaking through, but it's better
> >> than nothing.
> >
> > Maybe this would work:
> >
> > MACHINE_FEATURES_BACKFILL_CONSIDERED = "${MACHINE_FEATURES_BACKFILL}"
>
> I guess it doesn't work if MACHINE_FEATURES_BACKFILL_CONSIDERED is set
> elsewhere using _append.
>
> The real solution would probably be to skip backfilling
> MACHINE_FEATURES entirely for class-native?
Perhaps set MACHINE_FEATURES_forcevariable = "" in native.bbclass?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-03-23 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 22:47 [PATCH] native.bbclass: clear MACHINE_FEATURES Andre McCurdy
2017-03-23 9:06 ` Mike Looijmans
2017-03-23 18:59 ` Andre McCurdy
2017-03-23 19:09 ` Patrick Ohly [this message]
2017-03-23 19:26 ` Andre McCurdy
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=1490296143.6396.253.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=armccurdy@gmail.com \
--cc=mike.looijmans@topic.nl \
--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.