From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Build doesn't interrupt cleanly
Date: Thu, 20 Jun 2013 06:22:55 +0100 [thread overview]
Message-ID: <51C291AF.1070508@mlbassoc.com> (raw)
Using Yocto master (1dd643b142c69ac9035e29bff11d02201638dc65)
I forcefully interrupted a bitbake build with ^C^C. When it
shut down, I made some changes to my local.conf and then tried
to fire it up again, only to get this error:
ERROR: Only one copy of bitbake should be run against a build directory
It looks like bitbake didn't totally get cleaned up in this case.
$ ps ax | grep bit
16319 pts/4 S 0:01 python /home/local/poky-multi/bitbake/bin/bitbake-worker decafbad
Killing this left over worker let me continue.
I've never seen this before, so perhaps it's new behaviour.
If it happens again, I'll file a bug.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2013-06-20 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 5:22 Gary Thomas [this message]
2013-06-20 10:25 ` Build doesn't interrupt cleanly Gary Thomas
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=51C291AF.1070508@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.