Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Mar 2009 23:20:02 GMT
From:      bf <bf2006a@yahoo.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/132620: widespread failure of port builds on recent 8-CURRENT with tmpfs WRKDIR
Message-ID:  <200903142320.n2ENK2tM087699@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/132620; it has been noted by GNATS.

From: bf <bf2006a@yahoo.com>
To: Mark Linimon <linimon@lonesome.com>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/132620: widespread failure of port builds on recent 8-CURRENT with tmpfs WRKDIR
Date: Sat, 14 Mar 2009 16:14:37 -0700 (PDT)

 --- On Sat, 3/14/09, Mark Linimon <linimon@lonesome.com> wrote:
 
 > From: Mark Linimon <linimon@lonesome.com>
 > Subject: Re: kern/132620: widespread failure of port builds on recent 8-CURRENT with tmpfs WRKDIR
 > To: "bf" <bf2006a@yahoo.com>
 > Cc: bug-followup@FreeBSD.org
 > Date: Saturday, March 14, 2009, 5:11 PM
 > OK, I've put them up on my account on freefall at:
 > 
 >  http://people.freebsd.org/~linimon/tmp/bash.log.2.gz.b64
 >  http://people.freebsd.org/~linimon/tmp/bash.log.3.gz.b64
 > 
 > mcl
 
 Thank you; I should have realized that what I gained in
 compression I might loose again after Yahoo's encoding.
 
 I only included the verbose log because I hoped it would
 help in a report that is otherwise scant in debugging
 information.
 
 I should mention that although I've only observed this 
 problem on tmpfs, and not in the limited ports-building 
 runs I've made recently on ufs, it may in fact _not_ be confined
 to tmpfs: I strongly suspect PR ports/132542 to be another
 manifestation of this problem.
 
 Regards,
            b.
 
 
       



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903142320.n2ENK2tM087699>