From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake-1.6 crashes on 'which'.
Date: Sun, 22 Oct 2006 18:41:00 +0100 [thread overview]
Message-ID: <1161538860.5545.7.camel@localhost.localdomain> (raw)
In-Reply-To: <ehemhq$f0s$1@sea.gmane.org>
On Sun, 2006-10-22 at 10:57 +0800, Rob Kramer wrote:
> Richard Purdie wrote:
> > The patch in 1.7 is for a different problem. I've just updated the 1.6
> > branch with the correct fix (add import bb to the top of shell.py).
>
> Thanks for that, it works again now. I still got the crash below, but that
> was after a bunch of reparse commands, which might have upset bitbake a bit
> perhaps.
I can't seem to reproduce that. Can you give a sequence of commands
which result in the failure?
Mickey: I suspect this is some problem with the shell's internal state?
Thanks,
Richard
next prev parent reply other threads:[~2006-10-22 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 7:02 Bitbake-1.6 crashes on 'which' Rob Kramer
2006-10-18 7:19 ` Rob Kramer
2006-10-21 12:10 ` Richard Purdie
2006-10-22 2:57 ` Rob Kramer
2006-10-22 17:41 ` Richard Purdie [this message]
2006-10-22 18:32 ` Michael 'Mickey' Lauer
2006-10-23 2:07 ` Rob Kramer
2006-10-18 8:04 ` Holger Freyther
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=1161538860.5545.7.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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