[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to m4/README,v [branch-1_4]
From: |
Eric Blake |
Subject: |
Changes to m4/README,v [branch-1_4] |
Date: |
Thu, 21 Sep 2006 13:07:02 +0000 |
CVSROOT: /sources/m4
Module name: m4
Branch: branch-1_4
Changes by: Eric Blake <ericb> 06/09/21 13:07:02
Index: README
===================================================================
RCS file: /sources/m4/m4/README,v
retrieving revision 1.1.1.1.2.3
retrieving revision 1.1.1.1.2.4
diff -u -b -r1.1.1.1.2.3 -r1.1.1.1.2.4
--- README 22 Aug 2006 16:13:38 -0000 1.1.1.1.2.3
+++ README 21 Sep 2006 13:07:02 -0000 1.1.1.1.2.4
@@ -10,6 +10,13 @@
If GNU `m4' is meant to serve GNU `autoconf', beware that `m4'
should be fully installed *prior to* configuring `autoconf' itself.
+Likewise, if you intend on hacking GNU `m4' from CVS, the bootstrap
+process requires that you first install a released copy of GNU `m4'.
+
+If you are just trying to build `m4' from a released tarball, you
+should not normally need to run `./bootstrap' or `autoreconf'; just go
+ahead and start with `./configure'. If you are trying to build `m4'
+from CVS, more information can be found in the CVS-only file HACKING.
In the subdirectory `examples' you will find various m4 files, ranging
from trivial test files to rather advanced macros. If you intend to
@@ -24,7 +31,7 @@
By using `./configure --enable-changeword', you get an experimental
feature which allows for changing the syntax of what is a "word" in
`m4'. This feature will not be present in m4 2.0, but will be
-replaced by other new features which provide the same capability, so
+replaced by other new features which provide similar capability, so
do not count on it.
Send bug reports to address@hidden'. A bug report is an adequate
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Changes to m4/README,v [branch-1_4],
Eric Blake <=