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)tantorlabs(dot)com |
Subject: | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Date: | 2025-07-02 14:46:40 |
Message-ID: | CAOYmi+=ORLb7mYdLRyrBE5ZGKd74HC4akLF-Vky-yPZCH38=yQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 2, 2025 at 5:45 AM Ivan Kush <ivan(dot)kush(at)tantorlabs(dot)com> wrote:
>
> Thanks for the clarification! I thought linker flags should be installed
> globally for all compilation targets.
Not for libcurl, since the libpq-oauth module split.
> Another question:
>
> Why don't we set LIBS in the configure in "checking for curl_multi_init"
> using LIBCURL_LIBS or LIBCURL_LDFLAGS?
> [...]
> Without these LIBCURL... variables we will check a system libcurl, not
> our local.
Ah, that's definitely a bug. I've tested alternate PKG_CONFIG_PATHs,
but I haven't regularly tested on systems that have no system libcurl
at all. So those header and lib checks need to be moved after the use
of LIBCURL_CPPFLAGS and LIBCURL_LDFLAGS to prevent a false failure.
Otherwise they're only useful for the LIBCURL_LDLIBS assignment.
I wonder if I should just get rid of those to better match the Meson
implementation... but the error messages from the checks will likely
be nicer than compilation failures during the later test programs. Hm.
(Thanks for the report!)
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2025-07-02 14:49:41 | Re: ALTER TABLE ALTER CONSTRAINT misleading error message |
Previous Message | Tom Lane | 2025-07-02 14:44:50 | Re: cpluspluscheck vs ICU again |