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

From Wolfgang Walther
Subject Re: [PoC] Federated Authn/z with OAUTHBEARER
Date
Msg-id 3ef2e077-396c-4953-b062-c28fe16d2749@technowledgy.de
Whole thread Raw
In response to Re: [PoC] Federated Authn/z with OAUTHBEARER  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: [PoC] Federated Authn/z with OAUTHBEARER
List pgsql-hackers
Jacob Champion:
>> libpq.a
>> libpq-oauth-18.a
>>
>> The libpq.a file has no references to dlopen, but plenty of references
>> to curl stuff.
> 
> Which references? libpq-oauth should be the only thing using Curl symbols:
> 
>      $ nm src/interfaces/libpq/libpq.a | grep --count curl
>      0
>      $ nm src/interfaces/libpq-oauth/libpq-oauth-18.a | grep --count curl
>      116

Not sure what I was looking at earlier, probably too many different 
builds at the same time. Now I can't find the curl symbols in libpq.a 
either...

>> I'm not sure what the libpq-oauth-18.a file is for.
> 
> That implements the flow. You'll need to link that into your
> application or it will complain about missing flow symbols. (I don't
> think there's an easy way to combine the two libraries in our Autoconf
> setup; the only ways I can think of right now would introduce a
> circular dependency between libpq and libpq-oauth...)

... which immediately explains what the libpq-oauth-18.a file is for, yes.

But that means we'd need a -lpq-oauth-18 or something like that in 
Libs.private in libpq.pc, right?

This seems to be missing, I checked both the autoconf and meson builds.

Best,

Wolfgang



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ci: Allow running mingw tests by default via environment variable
Next
From: Andrei Lepikhov
Date:
Subject: Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment