Re: package building failure irritation
- From: Dag-Erling Smørgrav <des@xxxxxx>
- Date: Mon, 01 Mar 2010 20:08:45 +0100
xorquewasp@xxxxxxxxxxxxxx writes:
Dag-Erling Smørgrav <des@xxxxxx> writes:
xorquewasp@xxxxxxxxxxxxxx writes:Basically because "I don't know any better".
There's certainly no parallel building going on, but /work is nullfsNot sure. Why are you using nullfs?
mounted (from ZFS). Could this cause the above?
That's begging the question... Clearly you're using nullfs because you
need something done that you think nullfs can do for you. I'd like to
know what that is, because I suspect that you don't actually need it,
and it might be the source of your problems.
DES
--
Dag-Erling Smørgrav - des@xxxxxx
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: package building failure irritation
- From: xorquewasp
- Re: package building failure irritation
- References:
- Re: package building failure irritation
- From: Dag-Erling Smørgrav
- Re: package building failure irritation
- From: xorquewasp
- Re: package building failure irritation
- From: Dag-Erling Smørgrav
- Re: package building failure irritation
- From: xorquewasp
- Re: package building failure irritation
- Prev by Date: Re: 32 bit Linux lseek missing overflow check (was: Re: Linuxolator patches: stat and lseek SEEK_END for disk devices)
- Next by Date: Re: `make cleanworld` and /usr/obj/lib32/usr/src
- Previous by thread: Re: package building failure irritation
- Next by thread: Re: package building failure irritation
- Index(es):
Relevant Pages
|