DragonFly BSD
DragonFly users List (threaded) for 2012-10
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Fwd: df64 pkgsrc 2012Q3 DragonFly 3.2/x86_64 2012-10-09 19:40


From: Justin Sherrill <justin@xxxxxxxxxxxxxxxxxx>
Date: Sun, 28 Oct 2012 12:31:00 -0400

On Sun, Oct 28, 2012 at 12:13 PM, Chris Turner
<c.turner@199technologies.com> wrote:
>
> If the 'stuck builds' were getting stuck because of autoconf 'conftest'
> programs getting stuck in a loop and never exiting, I had the same from
> my build of ~1mo ago - I did not get to the point of investigating
> the real problems, but running a little loop to kill conftest processes
> in another terminal let my build proceed without manual intervention.

I've see the conftest scripts getting stuck before.  This time, it
seemed to be mv operations.

10Oct12   0:01.05 /bin/mv -f
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool-63648.tmp
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool
10Oct12   0:00.59 /bin/mv -f
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool-63627.tmp
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool
10Oct12   0:00.71 /bin/mv -f
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool-63624.tmp
/wrkobjdir/x11/qt4-libs/work/.wrapper/tmp/cache-libtool
Mon07AM   0:00.60 /bin/mv -f
/wrkobjdir/audio/buzztard/work/.wrapper/tmp/cache-82016.tmp
/wrkobjdir/audio/buzztard/work/.wrapper/tmp/cache
Mon07AM   0:00.34 /bin/mv -f
/wrkobjdir/audio/buzztard/work/.wrapper/tmp/cache-81711.tmp
/wrkobjdir/audio/buzztard/work/.wrapper/tmp/cache
15Oct12   0:00.55 /bin/mv -f
/wrkobjdir/net/vinagre/work/.wrapper/tmp/cache-87371.tmp
/wrkobjdir/net/vinagre/work/.wrapper/tmp/cache
15Oct12   0:09.16 /bin/mv -f
/wrkobjdir/net/vinagre/work/.wrapper/tmp/cache-87138.tmp
/wrkobjdir/net/vinagre/work/.wrapper/tmp/cache


Francois Tigeot mentioned something similar on IRC, that he had a lot
of stuck mv processes.  Maybe having -j set is causing problems?
These all appear to come in pairs, and I think the third qt4-libs
operation comes from having retried that build.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]