Re: Windows: openssl & gssapi dislike each other

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Imran Zaheer <imran.zhir@gmail.com>

Cc: Andres Freund <andres@anarazel.de>, Dave Page <dpage@pgadmin.org>, Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2025-01-22T09:17:13Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Move GSSAPI includes into its own header
- e92c0632c147 18.0 landed
Tighten test_predtest's input checks, and improve error messages.
- 00ac25a3c365 17.0 cited
Collation documentation fixes.
- 8ba34c698d19 17.0 cited
contrib/sslinfo needs a fix too to make hamerkop happy.
- 568620dfd691 15.0 cited
Second attempt to silence SSL compile failures on hamerkop.
- 1241fcbd7e64 15.0 cited

> On 10 Jul 2024, at 19:06, Imran Zaheer <imran.zhir@gmail.com> wrote:

(Reviving an old thread to give them a chance to finish before v18)

> For now maybe we can do the future proofing for gssapi & openssl includes
> and do testing if openssl clashes with some other lib too.

Where did this end up, is compilation on Windows with OpenSSL and GSSAPI still
an issue?  AFAICT the fixes from this thread are yet to be applied and it would
be nice to have that done before v18 if still needed.

--
Daniel Gustafsson