Re: [PoC] Federated Authn/z with OAUTHBEARER - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: [PoC] Federated Authn/z with OAUTHBEARER
Date
Msg-id CAOYmi+=tktL4Pzwfyk_ODyUQPpWQaJs_sUgxtzaSKS2tVYgucw@mail.gmail.com
Whole thread Raw
In response to Re: [PoC] Federated Authn/z with OAUTHBEARER  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PoC] Federated Authn/z with OAUTHBEARER
Re: [PoC] Federated Authn/z with OAUTHBEARER
List pgsql-hackers
On Fri, May 2, 2025 at 11:26 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Yeah, they are both under /opt/local/include in a MacPorts setup.
> But disabling NLS doesn't break it for me.  I tried
>
> meson setup build --auto-features=disabled -Dlibcurl=enabled
>
> to make sure that /opt/local/include wasn't getting pulled in
> some other way, and it still builds.

Hm. If you clear out the build artifacts under
src/interfaces/libpq-oauth, and then build with

    $ ninja -v src/interfaces/libpq-oauth/libpq-oauth.a

does that help surface anything interesting?

> Apropos of that: our fine manual claims that option is spelled
> --auto_features, but that fails for me.  Is that a typo in our
> manual, or do some meson versions accept the underscore?

--auto_features doesn't work for me either. That looks like an
accidental mashup of --auto-features and -Dauto_features.

--Jacob



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Next
From: Tom Lane
Date:
Subject: Re: SQL functions: avoid making a tuplestore unnecessarily