package building failure irritation

[xorquewasp at googlemail.com]

On 2010-03-01 14:34:50, Dag-Erling Smørgrav wrote:
> % fgrep 'Directory not empty' inkscape.txt 
> rmdir: /work/ports/devel/boost-libs/work: Directory not empty
> rmdir: /work/ports/x11-toolkits/gtkmm24/work: Directory not empty
> rmdir: /work/ports/devel/boehm-gc/work: Directory not empty
> rmdir: /work/ports/math/gsl/work: Directory not empty
> rmdir: /work/ports/textproc/gtkspell/work: Directory not empty
> rmdir: /work/ports/graphics/libwpg/work: Directory not empty
> rmdir: /work/ports/graphics/ImageMagick/work: Directory not empty
> rmdir: /work/ports/textproc/p5-XML-XQL/work: Directory not empty
> rmdir: /work/ports/devel/boost-jam/work: Directory not empty
> rmdir: /work/ports/devel/icu/work: Directory not empty
> rmdir: /work/ports/devel/glibmm/work: Directory not empty
> rmdir: /work/ports/graphics/cairomm/work: Directory not empty
> rmdir: /work/ports/x11-toolkits/pangomm/work: Directory not empty
> 
> This tells me that either there is another build running in parallel, or
> /work is mounted from a dodgy NFS server.

'Lo,

There's certainly no parallel building going on, but /work is nullfs
mounted (from ZFS). Could this cause the above?

xw