Re: OpenSSL 1.1 breaks configure and more
Christoph Berg <myon@debian.org>
From: Christoph Berg <myon@debian.org>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Andreas Karlsson <andreas@proxel.se>
Date: 2016-06-27T18:12:12Z
Lists: pgsql-hackers
Re: Andreas Karlsson 2016-06-27 <8a0a5959-0b83-3dc8-d9e7-66ce8c1c5bc7@proxel.se> > > The errors you report make it sound like they broke API compatibility > > wholesale. Was that really their intent? If so, where are the changes > > documented? > > I do not see that they have documented the removal of the SSL_library_init > symbol anywhere. They changed the function into a macro in the following > commit. I guess we have to check for some other symbol, like SSL_new. I'm not an autoconf expert, but as said in the original mail, I could get the SSL_library_init check to work, even if that's a macro now: > - AC_CHECK_LIB(ssl, SSL_library_init, [], [AC_MSG_ERROR([library 'ssl' is required for OpenSSL])]) > + AC_CHECK_LIB([ssl], [SSL_library_init]) (I haven't investigated if that's due to the quoting, the removal of the extra arguments, or simply because I reran autoreconf.) > I think much of the above is missing from the release notes I have found. I > hope they will be more complete at the time of the release. I am working on > a patch to handle these API changes. > > - https://www.openssl.org/news/openssl-1.1.0-notes.html > - https://wiki.openssl.org/index.php/1.1_API_Changes Nod, I was also disappointed when browsing the API changes document, given it didn't mention any of the problems I was seeing. Christoph
Commits
-
Back-patch 9.4-era SSL renegotiation code into 9.3 and 9.2.
- fbfeceb25362 9.3.17 landed
- 58384149bdbd 9.2.21 landed