From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: v4 or so [PATCH 0/3] sanity.bbclass and friends: toolchain sanity
Date: Wed, 09 May 2012 16:32:17 -0700 [thread overview]
Message-ID: <4FAAFE81.8010600@linux.intel.com> (raw)
In-Reply-To: <cover.1335922726.git.peter.seebach@windriver.com>
On 05/01/2012 06:45 PM, Peter Seebach wrote:
> And yes, I'm aware that "toolchain sanity checks" is sort of a
> self-defeating concept.
>
> Okay, cleanups:
> * Now checking MULTILIB_VARIANTS, not MULTILIBS. Simpler and less indented.
> * Added a third commit to do the BBCLASSEXTEND checks since those seem like
> a good idea, and it's less work to do it than to create a todo item.
> * Did you know that, despite a lot of this being Python, you can't use
> triple-quote strings in documentation.conf? I didn't, and apparently
> that "fix" went in untested. (Also the addition of duplicate but indented
> copies of two later lines, which didn't parse. Looks like I got a bit
> careless with my cut and paste there.)
>
> The following changes since commit 35b5fb2dd2131d4c7dc6635c14c6e08ea6926457:
> Saul Wold (1):
> eglibc-package: remove /var
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib seebs/toolchains
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/toolchains
>
> Peter Seebach (3):
> conf/machine: Clean up configuration values.
> sanity.bbclass: Implement initial toolchain sanity checks
These 2 have been merged into OE-Core
> sanity.bbclass: Check for bogus values in BBCLASSEXTEND
>
RP commented on this one.
Thanks
Sau!
> meta/classes/sanity.bbclass | 86 ++++++++++++++++++++++
> meta/conf/documentation.conf | 9 ++
> meta/conf/machine/include/README | 4 +
> meta/conf/machine/include/arm/arch-armv5-dsp.inc | 1 +
> meta/conf/machine/include/arm/arch-armv7a.inc | 2 +-
> meta/conf/machine/include/ia32/arch-ia32.inc | 2 +-
> meta/conf/machine/include/mips/arch-mips.inc | 6 +-
> meta/conf/machine/include/tune-c3.inc | 2 +-
> 8 files changed, 106 insertions(+), 6 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-05-09 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 1:45 v4 or so [PATCH 0/3] sanity.bbclass and friends: toolchain sanity Peter Seebach
2012-05-02 1:45 ` [PATCH 1/3] conf/machine: Clean up configuration values Peter Seebach
2012-05-02 1:45 ` [PATCH 2/3] sanity.bbclass: Implement initial toolchain sanity checks Peter Seebach
2012-05-02 1:45 ` [PATCH 3/3] sanity.bbclass: Check for bogus values in BBCLASSEXTEND Peter Seebach
2012-05-09 20:59 ` Richard Purdie
2012-05-09 21:09 ` Peter Seebach
2012-05-09 23:32 ` Saul Wold [this message]
2012-05-09 23:58 ` v4 or so [PATCH 0/3] sanity.bbclass and friends: toolchain sanity Peter Seebach
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=4FAAFE81.8010600@linux.intel.com \
--to=sgw@linux.intel.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