database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

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

Browse Source 
RELEASE_CHANGES.

Manfred Koizar
This commit is contained in:
Bruce Momjian 2003-01-11 04:59:08 +00:00
parent e2123a9708
commit 295ece4a0c
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
configure vendored
View File

@ -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; }; }

4
configure.in
View File

@ -1,5 +1,5 @@
dnl Process this file with autoconf to produce a configure script.
dnl $Header: /cvsroot/pgsql/configure.in,v 1.217.2.6 2002/12/18 02:07:20 momjian Exp $
dnl $Header: /cvsroot/pgsql/configure.in,v 1.217.2.7 2003/01/11 04:59:07 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

2
src/tools/RELEASE_CHANGES
View File

@ -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.