kern/132620: widespread failure of port builds on recent 8-CURRENT with tmpfs WRKDIR

[bf]

The following reply was made to PR kern/132620; it has been noted by GNATS.

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

 It looks as if the text in my last follow-up isn't displayed
 correctly on the PR page, so here it is again:
 
 
 --- On Sun, 3/15/09, bf <bf2006a at yahoo.com> wrote:
 
 > From: bf <bf2006a at yahoo.com>
 > Subject: Re: kern/132620: widespread failure of port builds on recent 8-CURRENT with tmpfs WRKDIR
 > To: "Mark Linimon" <linimon at lonesome.com>
 > Cc: bug-followup at FreeBSD.org
 > Date: Sunday, March 15, 2009, 7:33 AM
 > Yes, unfortunately this is definitely occurring on ufs as
 > well.
 > On a gjournaled ufs /usr filesystem using 8.0-CURRENT amd64
 > r189848 this morning, I attempted to build
 > src/usr.bin/systat and
 > encountered this problem again.  Oddly, when repeating the
 > build
 > while using script(1) to record it, the build succeeded.
 > After
 > exiting script(1), and trying a third build without it, the
 > build
 > failed again.  Transcripts with and without script(1)
 > attached.
 > 
 > This was using an account with the most recent version of
 > the
 > shells/bash port as the login shell.  Switching to an
 > account
 > that uses bin/sh, I tried the build yet again and it
 > succeeded.
 > However, I have observed this problem when bin/sh is the
 > login
 > shell in other examples.
 > 
 > Strangely, 287 port builds succeeded on the same machine
 > this morning using the /usr/tmp directory as WRKDIRPREFIX
 > and bash as the login shell without any hint of this
 > problem.
 > 
 > Regards,
 >          b.