m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/README,v


From: Eric Blake
Subject: Changes to m4/README,v
Date: Sat, 10 Jun 2006 15:17:14 +0000

CVSROOT:        /sources/m4
Module name:    m4
Changes by:     Eric Blake <ericb>      06/06/10 15:17:11

Index: README
===================================================================
RCS file: /sources/m4/m4/README,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- README      4 May 2005 15:45:43 -0000       1.7
+++ README      10 Jun 2006 15:17:11 -0000      1.8
@@ -5,12 +5,14 @@
 running shell commands, doing arithmetic, etc.  Autoconf needs GNU
 `m4' for generating `configure' scripts, but not for running them.
 
-GNU `m4' has been originally written by René Seindal, from Denmark.
+GNU `m4' has been originally written by Rene' Seindal, from Denmark.
 
-GNU `m4' has a web site at http://www.seindal.dk/rene/gnu/.
+GNU `m4' has a web site at http://www.gnu.org/software/m4/.
 
 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'.
 
 In the subdirectories `tests' and `examples' you will find various m4
 files, ranging from trivial test files to rather advanced macros.  If
@@ -47,11 +49,6 @@
 reason, compilation of shared libraries can be turned off by
 specifying the `--disable-shared' option to `configure'.
 
-When compiling on cygwin (b20.1 at least), the cygwin getopt build
-doesn't handle optional arguments properly.  The best way to get around
-this is to force the build to use the included getopt files like this,
-`ac_cv_func_getopt_long=no ./configure`.
-
 Send bug reports, comments or ideas to address@hidden'.  A bug report
 is an adequate description of the problem: your input, what you
 expected, what you got, and why this is wrong.  Diffs are welcome, but




reply via email to

[Prev in Thread] Current Thread [Next in Thread]