From: Paul Sokolovsky <pmiscml@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: oe for two target boards at the same time
Date: Tue, 9 Oct 2007 19:52:55 +0300 [thread overview]
Message-ID: <153769710.20071009195255@gmail.com> (raw)
In-Reply-To: <1191926182.20582.22.camel@localhost.localdomain>
Hello Richard,
Tuesday, October 9, 2007, 1:36:22 PM, you wrote:
> On Tue, 2007-10-09 at 11:02 +0200, pHilipp Zabel wrote:
>> On 10/9/07, Koen Kooi <k.kooi@student.utwente.nl> wrote:
>> > If you already built binutils you can remove MACHINE=<foo> from conf files and
>> > set it in env, e.g. :
>> >
>> > MACHINE=c7x0 bitbake mono ; MACHINE=fic-gta01 bitbake mono
>> >
>> > that saves you a complete reparse.
>>
>> Isn't the binutils MACHINE environment variable issue fixed by now?
>> I only just noticed that I don't know because I have MACHINE?=magician
>> somewhere and always seem to do the first build without the MACHINE
>> envvar set...
> The issue should be fixed. I regularly make builds with a MACHINE ?=
> entry but with MACHINE set in the environment too and it all seems to
> work.
> People keep telling me there is a problem but I've not seen any
> reproducible test case...
Thanks for bringing this up. Not yet, not yet. Following patch was
produced to fix another manifestation of the issue, hopefully forever:
Index: lib/bb/data.py
===================================================================
--- lib/bb/data.py (revision 974)
+++ lib/bb/data.py (working copy)
@@ -370,18 +370,19 @@
if type(val) is not types.StringType:
return 0
- if getVarFlag(var, 'matchesenv', d):
- return 0
-
if (var.find("-") != -1 or var.find(".") != -1 or var.find('{') != -1 or var.find('}') != -1 or var.find('+') != -1) and not all:
return 0
varExpanded = expand(var, d)
+ # Unexporting is the highest priority
if unexport:
o.write('unset %s\n' % varExpanded)
return 1
+ if getVarFlag(var, 'matchesenv', d):
+ return 0
+
val.rstrip()
if not val:
return 0
The idea is simple: if a var is marked as unexported, then it should
be unset unconditionally regardless of any other circumstances ;-).
So, I hit this issue on a RedHat-based system (FC5). Otherwise, it
seemed to have worked on Debian/Gentoo systems.
> Cheers,
> Richard
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-10-09 16:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 10:41 hello Tobias Pflug
2007-10-04 11:18 ` hello Michael Krelin
2007-10-04 12:40 ` hello Holger Freyther
2007-10-04 12:55 ` monotone/git (was hello...) Tobias Pflug
2007-10-04 13:27 ` Holger Freyther
2007-10-04 13:50 ` Darcy Watkins
2007-10-04 13:52 ` Michael Krelin
2007-10-05 6:28 ` oe for two target boards at the same time Alex
2007-10-05 13:57 ` Cliff Brake
2007-10-05 15:47 ` Khem Raj
2007-10-06 8:19 ` Koen Kooi
2007-10-06 11:39 ` Marcin Juszkiewicz
2007-10-08 20:20 ` Cliff Brake
2007-10-09 8:28 ` Koen Kooi
2007-10-09 9:02 ` pHilipp Zabel
2007-10-09 10:36 ` Richard Purdie
2007-10-09 11:18 ` Graeme Gregory
2007-10-09 11:49 ` Graeme Gregory
2007-10-09 16:52 ` Paul Sokolovsky [this message]
2007-10-09 16:48 ` Paul Sokolovsky
2007-10-04 18:02 ` monotone/git (was hello...) Richard Purdie
2007-10-04 13:51 ` Michael Krelin
2007-10-04 13:30 ` Michael Krelin
2007-10-04 18:36 ` Chris Larson
2007-10-04 18:49 ` Tim Bird
2007-10-04 18:57 ` Chris Larson
2007-10-04 19:11 ` Michael Krelin
2007-10-04 19:27 ` Chris Larson
2007-10-04 19:39 ` Michael Krelin
2007-10-04 20:18 ` Chris Larson
2007-10-04 20:53 ` Michael Krelin
2007-10-04 19:08 ` Michael Krelin
2007-10-04 19:28 ` Chris Larson
2007-10-04 13:19 ` hello Michael Krelin
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=153769710.20071009195255@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rpurdie@rpsys.net \
/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