From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: do_rootfs fails
Date: Fri, 11 May 2007 20:24:17 +0200 [thread overview]
Message-ID: <4644B4D1.5010803@klever.net> (raw)
In-Reply-To: <4644B0D2.8020409@dominion.kabel.utwente.nl>
> All: Are we still going to wait 1.5 months with requiring 1.8.x? I've seen enough proof
> that 1.6.x is broken with current .dev, with no effort to fix it. "Giving people time to
> prepare the upgrade" has now turned into "Stabbing user in the eye" :(
There's also an option of asking Tom to bitbake -DDD and send it to
zecke, because I couldn't find time to try BB 1.6 for him again. And let
him apply the patch that fixes this problem:
Index: lib/bb/parse/parse_py/BBHandler.py
===================================================================
--- lib/bb/parse/parse_py/BBHandler.py (revision 817)
+++ lib/bb/parse/parse_py/BBHandler.py (working copy)
@@ -66,7 +66,9 @@
if not file in __inherit_cache.split():
debug(2, "BB %s:%d: inheriting %s" % (fn, lineno, file))
__inherit_cache += " %s" % file
+ data.setVar('__inherit_cache', __inherit_cache, d)
include(fn, file, d)
+ __inherit_cache = data.getVar('__inherit_cache', d) or ""
data.setVar('__inherit_cache', __inherit_cache, d)
Love,
H
next prev parent reply other threads:[~2007-05-11 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 17:45 do_rootfs fails Tom Walsh
2007-05-11 18:07 ` Koen Kooi
2007-05-11 18:24 ` Michael Krelin [this message]
2007-05-12 21:33 ` Stelios Koroneos
2007-05-19 17:50 ` Richard Purdie
2007-05-12 0:07 ` Matthias Hentges
2007-05-12 10:28 ` Koen Kooi
2007-05-14 12:42 ` Richard Purdie
2007-05-14 22:23 ` Matthias Hentges
-- strict thread matches above, loose matches on Subject: below --
2013-04-09 8:07 Jaap de Jong
2013-04-09 11:37 ` Jaap de Jong
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=4644B4D1.5010803@klever.net \
--to=hacker@klever.net \
--cc=openembedded-devel@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