A tiny patch to fix a typo in configure.in and another one in

RELEASE_CHANGES.

Manfred Koizar

diff --git a/configure b/configure
index 1579d312738c5e722554a1abf5dd29f6b15aa456..8c0d3cbf53223fb2c9b1ee03e7e233db80008ce6 100755 (executable)
--- a/configure
+++ b/configure
@@ -7756,11 +7756,11 @@ if test $ac_cv_header_zlib_h = yes; then
   :
 else
   { { echo "$as_me:$LINENO: error: zlib header not found
-If you have readline already installed, see config.log for details on the
+If you have zlib already installed, see config.log for details on the
 failure.  It is possible the compiler isn't looking in the proper directory.
 Use --without-zlib to disable zlib support." >&5
 echo "$as_me: error: zlib header not found
-If you have readline already installed, see config.log for details on the
+If you have zlib already installed, see config.log for details on the
 failure.  It is possible the compiler isn't looking in the proper directory.
 Use --without-zlib to disable zlib support." >&2;}
    { (exit 1); exit 1; }; }

diff --git a/configure.in b/configure.in
index f004849c561059b06c5d88633be9c90fc567a452..0e39dc3f4f25a45d8017a6a7f153592b598f5ee0 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -704,7 +704,7 @@ fi
 
 if test "$with_zlib" = yes; then
   AC_CHECK_HEADER(zlib.h, [], [AC_MSG_ERROR([zlib header not found
-If you have readline already installed, see config.log for details on the
+If you have zlib already installed, see config.log for details on the
 failure.  It is possible the compiler isn't looking in the proper directory.
 Use --without-zlib to disable zlib support.])])
 fi

diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES
index 52c98360f4abda769ddb833e624dfb13366c5f90..e0a0bacad2083e66d45095c52b3b13e2df94ef46 100644 (file)
--- a/src/tools/RELEASE_CHANGES
+++ b/src/tools/RELEASE_CHANGES
@@ -41,7 +41,7 @@ but are not limited to:
 
 3. Removing a field from a public structure.
 
-3. Adding a field to a public structure, unless steps have been
+4. Adding a field to a public structure, unless steps have been
 previously taken to shield users from such a change, for example by
 such structures only ever being allocated/instantiated by a library
 function which would give the new field a suitable default value.