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>

Date: 2025-05-12T16:08:25Z

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 Mon, May 12, 2025 at 8:49 AM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
>
> On Mon, May 12, 2025 at 3:50 AM Christoph Berg <myon@debian.org> wrote:
> > Since nothing in libpq should need curl for compiling, should we drop
> > it there instead?
>
> The static build (libpq.a) still needs libcurl. The module is only
> compiled for use by the shared library.

Sorry, typing too fast in the airport. The _clients_ of libpq.a still
need libcurl, after they link libpq-oauth.a for the missing symbols.
Isn't that what Requires.private is for?

--Jacob