| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com |
| Subject: | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
| Date: | 2024-04-05 21:53:22 |
| Message-ID: | CAOYmi+=MGq_Zq_zkhQTe0S_fzUtWNMhG8xkg7N+jt0uQ7E+5kA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 5, 2024 at 2:48 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> But does that actually work? If I change the API_COMPAT to the 1.1.1 version
> number and run configure against 1.0.2 it passes just fine. Am I missing some
> clever trick here?
Similarly, I changed my API_COMPAT to a nonsense 0x90100000L and
- a 1.1.1 build succeeds
- a 3.0 build fails
- LibreSSL doesn't appear to care or check that #define at all
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cary Huang | 2024-04-05 22:27:51 | Re: Add last_commit_lsn to pg_stat_database |
| Previous Message | Daniel Gustafsson | 2024-04-05 21:48:30 | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |