Module Name: src
Committed By: apb
Date: Wed Jul 23 08:52:32 UTC 2014
Modified Files:
src: UPDATING
Log Message:
More general advice about "cvs [update aborted]... No such file
or directory".
Also invent a "Cause:" keyword for use in "Symptom:/Cause:/Fix" sections.
Also add a note near the top of the file saying that there are
several sections marked by "^^^".
To generate a diff of this commit:
cvs rdiff -u -r1.256 -r1.257 src/UPDATING
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/UPDATING
diff -u src/UPDATING:1.256 src/UPDATING:1.257
--- src/UPDATING:1.256 Wed Jul 23 08:37:03 2014
+++ src/UPDATING Wed Jul 23 08:52:32 2014
@@ -1,4 +1,4 @@
-$NetBSD: UPDATING,v 1.256 2014/07/23 08:37:03 apb Exp $
+$NetBSD: UPDATING,v 1.257 2014/07/23 08:52:32 apb Exp $
This file (UPDATING) is intended to be a brief reference to recent
changes that might cause problems in the build process, and a guide for
@@ -11,6 +11,9 @@ Note that much of the advice in this UPD
build.sh existed. Nevertheless, the advice here may be useful for
working around specific problems with build.sh.
+Sections are marked with "^^^^^". After the section on "Recent changes"
+are several sections containing more general information.
+
See also: BUILDING, build.sh, Makefile.
Recent changes:
@@ -677,3 +680,13 @@ Fix: May need to build & install libs
Symptom:Update build fails in src/tools/gcc complaining that a variable
(e.g. CPPFLAGS) has changed since the previous run.
Fix: Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
+
+Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
+ No such file or directory.
+Cause: If a directory is created by mistake, then it is sometimes
+ deleted from the CVS repository using administrative commands
+ that bypass the normal cvs access controls. If your cvs working tree
+ contains references to a directory that has been deleted on the
+ server in this way, then "cvs update" reports this error.
+Fix: Recursively delete the affected directory from your working tree
+ and try the update again.
