diff options
| -rwxr-xr-x | configure | 4 | ||||
| -rw-r--r-- | configure.in | 4 | ||||
| -rw-r--r-- | src/tools/RELEASE_CHANGES | 2 |
3 files changed, 5 insertions, 5 deletions
diff --git a/configure b/configure index 09bdf98340c..d0d1682c7fc 100755 --- 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 b7d5958f7f4..ad801d1e777 100644 --- a/configure.in +++ b/configure.in @@ -1,5 +1,5 @@ dnl Process this file with autoconf to produce a configure script. -dnl $Header: /cvsroot/pgsql/configure.in,v 1.231 2003/01/09 14:34:53 petere Exp $ +dnl $Header: /cvsroot/pgsql/configure.in,v 1.232 2003/01/11 04:58:44 momjian Exp $ dnl dnl Developers, please strive to achieve this order: dnl @@ -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 52c98360f4a..e0a0bacad20 100644 --- 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. |