On 2012-02-23 20:28, Tom Lane wrote:
Hmmm ... I'd be happier with this patch if it reversed the order of the
library probes (ie, try the nonstandard names first), as then it would
obviously not break any configurations that worked before. Would that
be OK from your point of view, or not?
It will be OK I guess.
Also, the syntax looks wrong --- shouldn't the new calls be
AC_SEARCH_LIBS?
Of course - my bad. I had to recreate a patch because I needed to return
back this autoconf version check and haven't retested it. I'm attaching
corrected and this time tested version. Sorry.
Regards
Tometzky
--
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
Winnie the Pooh
diff -urNP postgresql-9.1.2.orig/configure.in postgresql-9.1.2/configure.in
--- postgresql-9.1.2.orig/configure.in 2011-12-01 22:47:20.000000000 +0100
+++ postgresql-9.1.2/configure.in 2012-02-23 20:34:00.765244884 +0100
@@ -945,8 +945,8 @@
AC_CHECK_LIB(crypto, CRYPTO_new_ex_data, [], [AC_MSG_ERROR([library 'crypto' is required for OpenSSL])])
AC_CHECK_LIB(ssl, SSL_library_init, [], [AC_MSG_ERROR([library 'ssl' is required for OpenSSL])])
else
- AC_CHECK_LIB(eay32, CRYPTO_new_ex_data, [], [AC_MSG_ERROR([library 'eay32' is required for OpenSSL])])
- AC_CHECK_LIB(ssleay32, SSL_library_init, [], [AC_MSG_ERROR([library 'ssleay32' is required for OpenSSL])])
+ AC_SEARCH_LIBS(CRYPTO_new_ex_data, eay32 crypto, [], [AC_MSG_ERROR([library 'eay32' or 'crypto' is required for OpenSSL])])
+ AC_SEARCH_LIBS(SSL_library_init, ssleay32 ssl, [], [AC_MSG_ERROR([library 'ssleay32' or 'ssl' is required for OpenSSL])])
fi
fi
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
