On Tue, Oct 18, 2016 at 1:41 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Dave Page <dp...@postgresql.org> writes: >> On Tue, Oct 18, 2016 at 12:18 PM, Heikki Linnakangas <hlinn...@iki.fi> wrote: >>> On 18 October 2016 12:52:14 EEST, Dave Page <dp...@postgresql.org> wrote: >>>> Baiji: 0.9.8e >>>> Narwhal: 0.9.6b > >>> Hang on, I removed support for OpenSSL < 0.9.8 a while ago. Narwhal >>> shouldn't even compile with 0.9.6. > >> Oops, sorry - I found another copy in the Mingw installation that it >> must be using (Mingw/Msys was a mess back then). I only have the >> header files to go by, but it looks like the very first 0.9.8 release. > > Is it possible that there's a header-vs-executable version mismatch > contributing to the problem here? (Although you'd think we'd have > hit it before now, if so.)
Advertising
We're not actually calling the openssl binary are we? There's an openssl binary only in the Msys installation (the really old version), and headers/libraries but no executable in the Mingw installation. -- Dave Page PostgreSQL Core Team http://www.postgresql.org/ -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
