On Tue, 30 Aug 2005 15:55:04 +0100
Patrick Welche <prlw1@newn.cam.ac.uk> wrote:

> >   | > there doesn't appear to be any dependency to make sure that
> >   | > /root/.profile is created before trying to create the hardlink to it.
> >   | 
> >   | Me too. It also broke an autobuild.
> >   | 
> >   | My current guess is that revision 1.240 of "src/Makefile" caused this
> >   | problem. I need however to run another build to prove it.
> > 
> > That change triggers the problem, rather than being the cause.
> > I think the problem is in <bsd.links.mk>'s handling of configlinksinstall.
> > I have a patch I'm testing; once that works I'll commit it.
> 
> I wonder: on the build.sh -j6 release run before hitting the .profile
> problem mentioned, I hit something like pax: no such directory and
> now of course I can't remember which one but it was in DESTDIR and
> had <arch> in it, and possibly even "include". Looking on the
> filesystem, that directory *did* exist. The point there is that I
> started from a newfs'd /usr/obj, with no obj.i386 links in /usr/src.
> Running build.sh -j6 -o -u release got passed that warning and on
> to the .profile problem.  Rerunning again got me a successful build :-)

I got both "include" and ".profile" problems. See toolchain/31082.
("strange error" I mentioned is ".profile" problem)

--
FUKAUMI Naoki