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

From Christoph Berg
Subject Re: "openssl" should not be optional
Date
Msg-id aNQqC4cpeJOqFPJ7@msg.df7cb.de
Whole thread Raw
In response to Re: "openssl" should not be optional  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Re: Daniel Gustafsson
> > 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.

Because I had already added openssl to 17's build-dependencies and
forgot to port that change to 18 *blush*:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096243

Christoph



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench
Next
From: Nathan Bossart
Date:
Subject: Re: a couple of small patches for simd.h