From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Fix typo in meta/classes/sanity.bbclass
Date: Mon, 10 Oct 2011 21:37:48 +0100 [thread overview]
Message-ID: <1318279077.23801.64.camel@ted> (raw)
In-Reply-To: <CAEsOVNfpf97anznqn8ZqgOXmJEZp3sA4pK7aALT2w=3G2SjPbA@mail.gmail.com>
On Mon, 2011-10-10 at 18:21 +0000, McClintock Matthew-B29882 wrote:
> Ping? Any comments?
>
> -M
>
> On Mon, Oct 3, 2011 at 6:48 PM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
> > On Mon, Oct 3, 2011 at 6:39 PM, Matthew McClintock <msm@freescale.com> wrote:
> >> Signed-off-by: Matthew McClintock <msm@freescale.com>
> >
> > Whoops =)
> >
> >> ---
> >> Not sure if this is correct but it looks like a typo, also
> >> there appears to be some issues with the fix as well
> >>
> >> meta/classes/sanity.bbclass | 2 +-
> >> 1 files changed, 1 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> >> index 4067408..cf30927 100644
> >> --- a/meta/classes/sanity.bbclass
> >> +++ b/meta/classes/sanity.bbclass
> >> @@ -169,7 +169,7 @@ def check_sanity_validmachine(e):
> >> messages = messages + 'TUNE_ARCH is unset. Please ensure your MACHINE configuration includes a valid tune configuration file which will set this correctly.\n'
> >>
> >> # Check TARGET_ARCH is set correctly
> >> - if data.getVar('TARGE_ARCH', e.data, False) == '${TUNE_ARCH}':
> >> + if data.getVar('TARGET_ARCH', e.data, False) == '${TUNE_ARCH}':
> >> messages = messages + 'TARGET_ARCH is being overwritten, likely by your MACHINE configuration files.\nPlease use a valid tune configuration file which should set this correctly automatically\nand avoid setting this in the machine configuration. See the OE-Core mailing list for more information.\n'
> >>
> >> # Check TARGET_OS is set
> >
> > After fixing this I see the following:
> >
> > ERROR: Poky's config sanity checker detected a potential misconfiguration.
> > Either fix the cause of this error or at your own risk disable the
> > checker (see sanity.conf).
> > Following is the list of potential problems / advisories:
> >
> > TARGET_ARCH is being overwritten, likely by your MACHINE
> > configuration files.
> > Please use a valid tune configuration file which should set this
> > correctly automatically
> > and avoid setting this in the machine configuration. See the OE-Core
> > mailing list for more information.
> >
> > ERROR: Execution of event handler 'check_sanity_eventhandler' failed
I've been meaning to check OECore to ensure this isn't going to cause
failures before adding the patch. I then forgot I needed to do this,
sorry :/. What I don't want to do is merge something which breaks things
for everyone...
Cheers,
Richard
prev parent reply other threads:[~2011-10-10 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 23:39 [RFC] Fix typo in meta/classes/sanity.bbclass Matthew McClintock
2011-10-03 23:48 ` McClintock Matthew-B29882
2011-10-10 18:21 ` McClintock Matthew-B29882
2011-10-10 20:37 ` Richard Purdie [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=1318279077.23801.64.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox