Skip to contentSkip to conversation

Build doesn't interrupt cleanly

DISCUSSION Gary Thomas 1 participant 2 messages Jun 20, 2013

lore
Share & tools
lore
#0 lore 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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 7 lines · Gary Thomas

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

Quoted 9 lines

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.

Looks like this was reported as bug #4750 only yesterday :-)

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------