Robert Nestor <rnestor%mac.com@localhost> writes: > While building some packages under the newly installed 10.0_BETA > system on a SATA HD, I’ve occasionally seen a build fail with > “directory not found”. But the directory does exist and re-executing > the package build command (without first cleaning the work build tree) > always succeeds. Again, it seems like the command that created the > directory to be used in the build process didn’t complete before the > directory needed to be accessed. In building about 400 packages I’ve > seen this happen twice, the last time being in the build of seamonkey. This is perhaps a package that needs MAKE_JOBS_SAFE=no. Try building with MAKE_JOBS=1 to diagnose. However it could also be related to your first point (and might not be).
Attachment:
signature.asc
Description: PGP signature