From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
---|---|
To: | Ivan Kush <ivan(dot)kush(at)tantorlabs(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, lev(dot)nikolaev(at)tantolabs(dot)com |
Subject: | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Date: | 2025-06-23 15:32:26 |
Message-ID: | CAOYmi+mRmRHD-fhXErR0kNqL5NMebPw1EEx++mgmrMAwLszCyw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 20, 2025 at 3:08 AM Ivan Kush <ivan(dot)kush(at)tantorlabs(dot)com> wrote:
>
> Hello!
>
> This patch fixes CPPFLAGS, LDFLAGS, LIBS when checking AsyncDNS libcurl
> support in configure
Hi Ivan, thanks for the report! Your patch puts new logic directly
after an AC_MSG_ERROR() call, so any effect has to come from the fact
that we're no longer restoring the old compiler and linker flags.
That's not what we want -- Curl needs to be isolated from the rest of
the build.
Let's focus on the error you're seeing:
> After compilation during testing some Postgres shared libraries or
> binaries that was linked with libcurl showed an error "version
> CURL_OPENSSL_3 not found (required by …/libcurl.so.4)"
What's your configure line? You need to make sure that your custom
libcurl is used at configure-time, compile-time, and run-time.
And which binaries are complaining? The only thing that should ever be
linked against libcurl is libpq-oauth-18.so.
Thanks,
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2025-06-23 15:38:40 | Re: Fixes inconsistent behavior in vacuum when it processes multiple relations |
Previous Message | Tom Lane | 2025-06-23 15:29:32 | Re: Improve CRC32C performance on SSE4.2 |