From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "openssl" should not be optional |
Date: | 2025-09-24 15:49:11 |
Message-ID: | A84FCF9B-F0C7-4B48-9EE0-0D163AFD17A9@yesql.se |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 24 Sep 2025, at 17:13, Christoph Berg <myon(at)debian(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Banck | 2025-09-24 15:52:02 | Re: GNU/Hurd portability patches |
Previous Message | Tom Lane | 2025-09-24 15:37:51 | Re: GNU/Hurd portability patches |