Re: "openssl" should not be optional - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: "openssl" should not be optional
Date
Msg-id A84FCF9B-F0C7-4B48-9EE0-0D163AFD17A9@yesql.se
Whole thread Raw
In response to Re: "openssl" should not be optional  (Christoph Berg <myon@debian.org>)
Responses Re: "openssl" should not be optional
List pgsql-hackers
> On 24 Sep 2025, at 17:13, Christoph Berg <myon@debian.org> wrote:
>
> Re: Daniel Gustafsson
>> Looking at this I was reminded that we already handle this by using a fallback
>> and the test worked all along.  The message for this was quite poorly worded
>> though, and used a warning instead of a note.  The attached will try to detect
>> openssl being missing before trying to run it, and will skip the warning
>> message if the fallback is used (which really isn't a warning in the first
>> place).
>
> Thanks, I just built the postgresql-18 again with this patch (and
> openssl not installed [*]). It passes fine now.
>
> In the meantime, I also got the report that postgresql-17 is not
> failing in that environment, so the problem is new in 18.

That's odd, off the cuff I don't see anything materially different around this
but I'll do some more digging.  It will at least be fixed by 18.1.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GNU/Hurd portability patches
Next
From: Michael Banck
Date:
Subject: Re: GNU/Hurd portability patches