Re: Waiting for unfinished jobs....
On Tue, Oct 26, 2004 at 10:06:48AM +1000, Anibal Monsalve Salazar wrote:
> Hello,
>
> Package harbour is FTBFS on alpha, s390, m68k, powerpc and mips, as
> you can see at:
>
> http://buildd.debian.org/build.php?pkg=harbour
>
> Could someone shed some light on this problem?
>
> A build log extract follows.
>
> [...]
> gcc -I. -I../../../../include -Wall -g -c ../../hbmlang.c -ohbmlang.o
> ../../../../source/compiler/linux/gcc/harbour ../../hbmake.prg -n -q0 -w -es2 -gc0 -I../../ -I../../../../include
> make[4]: *** wait: No child processes. Stop.
> make[4]: *** Waiting for unfinished jobs....
> make[4]: *** wait: No child processes. Stop.
> make[3]: *** [descend] Error 2
> make[1]: *** [first] Terminated
> make[2]: *** [first] Terminated
> make: *** [build-stamp] Terminated
> Build killed with signal 15 after 150 minutes of inactivity
> [...]
This is usually an internal buildd issue, and shouldn't be your problem.
In an attempt to prevent builds from using up too much buildd resources,
sbuild (the program in the buildd suite which does the actual building)
keeps an internal timer for every build that is running; if no output
arrives in the log file within that time, the build is killed for fear
of a loop. The default time which is allocated to a build is 150
minutes; the messages you see originate from make receiving SIGTERM.
If it is indeed expected behaviour that the harbour build is silent for
more than 150 minutes in a row, then the timeout will have to be
increased (this can be done on a per-package, per-buildd basis), and the
build retried, but this is part of the routine maintenance of a buildd.
If your package is not in either 'building' of 'needs-build' on an
architectur after having been built with such a result, then please
contact the buildd admins of the architecture involved; they'll be able
to tell you why this was done.
--
EARTH
smog | bricks
AIR -- mud -- FIRE
soda water | tequila
WATER
-- with thanks to fortune
Reply to: