Subject: Re: Build race conditions, any solution?
To: None <Richard.Earnshaw@arm.com>
From: Robert Elz <kre@munnari.OZ.AU>
List: current-users
Date: 03/12/2002 22:05:23
    Date:        Tue, 12 Mar 2002 14:22:07 +0000
    From:        Richard Earnshaw <rearnsha@arm.com>
    Message-ID:  <200203121422.OAA27014@cam-mail2.cambridge.arm.com>

  | Sure.  There's more than one way to skin a cat, as they say.  But 
  | sometimes it's necessary to do a make clean, or even cleandir before 
  | trying to do a build after an update.

That I had done.   Just in case I had a mangled checkout somehow (this
was happening around the time of the rsync problems, not that they
turned out to be relevant) I even blew away my entire /usr/src and
checked the whole thing out again.

Make clean (and make cleandir) don't throw away /usr/include ...

note I was using -D / for my build (inside my new environment).  Not
doing that wouldn't have helped, as if I'd started somewhere clean,
everything would have worked OK, but then I'd have needed to build it
all again into / anyway (I don't want to copy from one place to
another, too many possibilities to mess something up doing that).

  | cvs update should allow you to get away with not having to delete 
  | everything.  Other tools/methods may not...

This is just something that probably needs to be made clear somewhere.

It is possible that simply installing include files with (the equiv of) cp -p
might make most of the problem go away.

kre