[oe] oe for two target boards at the same time
Paul Sokolovsky
pmiscml at gmail.com
Tue Oct 9 16:52:55 UTC 2007
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 at 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 at gmail.com
More information about the Openembedded-devel
mailing list