Re: libcurl in libpq.pc
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Christoph Berg <myon@debian.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Wolfgang Walther <walther@technowledgy.de>, Timo Röhling <roehling@debian.org>
Date: 2025-09-23T21:15:28Z
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 →
-
oauth: Correct missing comma in Requires.private
- a8f093234d78 18.0 landed
On Tue, Sep 23, 2025 at 12:42 PM Christoph Berg <myon@debian.org> wrote: > Maybe by the letter, but I think we have a real problem and need to do > something. If I break Wolfgang's use case again, we will still have a real problem. > > I think we can't avoid it; if anyone wants to get Windows support > > working they'll need -DCURL_STATICLIB as provided by libcurl.pc. > > That would be in Cflags.private. Yes. > > > $ pkgconf --libs --static libpq > > > -lpq -lpgcommon -lpgport -lpq-oauth -lssl -lcrypto -lgssapi_krb5 -lm -lldap -lcurl -lssl -lz -lzstd -ldl -pthread -lcrypto -lz -lzstd -ldl -pthread > > > > Prettier, but wrong? I don't think that's going to link, is it? > > Wrong how? It doesn't link. You'll be missing an incredible number of symbols. --Jacob