Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/3] Move architecture specific TARGET_OS mangling into tune files
Date: Wed, 27 Jul 2011 17:37:55 +0100	[thread overview]
Message-ID: <1311784675.2344.408.camel@rex> (raw)
In-Reply-To: <1311611027.30326.252.camel@phil-desktop>

On Mon, 2011-07-25 at 17:23 +0100, Phil Blundell wrote:
> On Mon, 2011-07-25 at 14:42 +0100, Richard Purdie wrote:
> > To try and help preserve my sanity when pulling the various multilib
> > patches together, I've merged these six patches, along with a patch
> > incrementing bitbake's miniumum version requirement for the
> > bb.utils.contains usage.
> 
> FWIW, the bitbake minimum version check (at least in its current form)
> doesn't buy much in this sort of situation because you get a parse error
> before the event handler in sanity.bbclass ever runs.  I think this
> happened last time there was a bitbake-affecting change too although I
> don't recall the details.
> 
> Perhaps adding something like:
> 
> __sane_bitbake := "${oe.check_bb_version_sanity}"
> 
> to the top of bitbake.conf would improve matters, I dunno.

Ouch, yes, we probably should do something like this.

Cheers,

Richard




      reply	other threads:[~2011-07-27 16:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 14:49 [PATCH 0/3] First round of tune config file updates Richard Purdie
2011-07-22 14:49 ` [PATCH 1/3] bitbake.conf/cross.bbclass: Add ability to dynamically change library location Richard Purdie
2011-07-22 14:49 ` [PATCH 2/3] conf/machine/tune: Overhaul tune include file variables Richard Purdie
2011-07-22 15:03   ` Kumar Gala
2011-07-22 15:13     ` Richard Purdie
2011-07-22 14:49 ` [PATCH 3/3] conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH Richard Purdie
2011-07-22 14:54   ` Koen Kooi
2011-07-22 15:11     ` Richard Purdie
2011-07-22 15:15       ` Koen Kooi
2011-07-22 18:00 ` [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features Richard Purdie
2011-07-22 18:14   ` Tom Rini
2011-07-25 18:55     ` Mark Hatle
2011-07-25 19:34       ` Tom Rini
2011-07-25 19:39         ` Mark Hatle
2011-07-25 20:39         ` Phil Blundell
2011-07-25 20:43           ` Tom Rini
2011-07-22 18:00 ` [PATCH 4/3] bitbake.conf/classes: Variable cleanup Richard Purdie
2011-07-22 18:01 ` [PATCH 6/3] Move architecture specific TARGET_OS mangling into tune files Richard Purdie
2011-07-25 13:42   ` Richard Purdie
2011-07-25 16:23     ` Phil Blundell
2011-07-27 16: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=1311784675.2344.408.camel@rex \
    --to=richard.purdie@linuxfoundation.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