summaryrefslogtreecommitdiffstats
path: root/contrib/cvs/INSTALL
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>2004-06-10 19:05:38 +0000
committerpeter <peter@FreeBSD.org>2004-06-10 19:05:38 +0000
commit8416bda1d23bda4666a5b880a9d78eccaa640036 (patch)
tree7d97944b58f1e30ab542f9c3d6720b69314cec4d /contrib/cvs/INSTALL
parent3d101ef985844544d089e129157a94a0640fd246 (diff)
downloadFreeBSD-src-8416bda1d23bda4666a5b880a9d78eccaa640036.zip
FreeBSD-src-8416bda1d23bda4666a5b880a9d78eccaa640036.tar.gz
Import cvs-1.11.17 onto vendor branch.
Diffstat (limited to 'contrib/cvs/INSTALL')
-rw-r--r--contrib/cvs/INSTALL20
1 files changed, 3 insertions, 17 deletions
diff --git a/contrib/cvs/INSTALL b/contrib/cvs/INSTALL
index 81abe03..8ae3d15 100644
--- a/contrib/cvs/INSTALL
+++ b/contrib/cvs/INSTALL
@@ -257,21 +257,7 @@ VAX:
Building from source code under Unix:
-1) Some combinations of Automake and Autoconf versions may break the
- CVS build if file timestamps aren't set correctly and people don't
- have the same versions the developers do, so the rules to run them
- automatically aren't included in the generated Makefiles unless you run
- configure with --enable-maintainer-mode.
-
- The CVS Makefiles and configure script were built using Automake 1.7.9 and
- Autoconf 2.58, respectively.
-
- There is a known bug in Autoconf 2.57 that will prevent the configure
- scripts it generates from working on some platforms. Other combinations of
- autotool versions may or may not work. If you get other versions to work,
- please send a report to <bug-cvs@gnu.org>.
-
-2) Run "configure":
+1) Run "configure":
$ ./configure
@@ -385,7 +371,7 @@ Building from source code under Unix:
END OF NOTE FOR NDBM GUNK.
-3) Try to build it:
+2) Try to build it:
$ make
@@ -396,7 +382,7 @@ Building from source code under Unix:
compiler information, make output, and anything else you think
will be helpful.
-3a) Run the regression tests (optional).
+3) Run the regression tests (optional).
You may also wish to validate the correctness of the new binary by
running the regression tests. If they succeed, that is nice to
OpenPOWER on IntegriCloud