On Tue, Oct 18, 2016 at 2:34 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> On 10/18/2016 04:32 PM, Dave Page wrote:
>>
>> On Tue, Oct 18, 2016 at 1:41 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>
>>> Dave Page <dpage@postgresql.org> writes:
>>>>
>>>> On Tue, Oct 18, 2016 at 12:18 PM, Heikki Linnakangas <hlinnaka@iki.fi>
>>>> wrote:
>>>>>
>>>>> On 18 October 2016 12:52:14 EEST, Dave Page <dpage@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.)
>>
>>
>> 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.
>
>
> Nope.
>
> Any chance of updating the OpenSSL on that box, to see if it helps? I'd
> rather not spend time investigate this further, if it turns out to be a bug
> in an ancient version of OpenSSL.
The latest OpenSSL version won't even configure on there. I wonder if
it's finally time to retire that old machine...
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/