Jacob Champion <[email protected]> writes:
> 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?
$ rm -rf src/interfaces/libpq-oauth
$ ninja -v src/interfaces/libpq-oauth/libpq-oauth.a
[1/2] ccache cc -Isrc/interfaces/libpq-oauth/libpq-oauth.a.p
-Isrc/interfaces/libpq-oauth -I../src/interfaces/libpq-oauth
-Isrc/interfaces/libpq -I../src/interfaces/libpq -Isrc/port -I../src/port
-Isrc/include -I../src/include -I/opt/local/include
-I/opt/local/libexec/openssl3/include -fdiagnostics-color=always -Wall
-Winvalid-pch -O2 -g -isysroot
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.4.sdk
-fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wmissing-prototypes
-Wpointer-arith -Werror=vla -Werror=unguarded-availability-new -Wendif-labels
-Wmissing-format-attribute -Wcast-function-type -Wformat-security
-Wdeclaration-after-statement -Wmissing-variable-declarations
-Wno-unused-command-line-argument -Wno-compound-token-split-by-macro
-Wno-format-truncation -Wno-cast-function-type-strict -MD -MQ
src/interfaces/libpq-oauth/libpq-oauth.a.p/oauth-curl.c.o -MF
src/interfaces/libpq-oauth/libpq-oauth.a.p/oauth-curl.c.o.d -o
src/interfaces/libpq-oauth/libpq-oauth.a.p/oauth-curl.c.o -c
../src/interfaces/libpq-oauth/oauth-curl.c
[2/2] rm -f src/interfaces/libpq-oauth/libpq-oauth.a && ar csr
src/interfaces/libpq-oauth/libpq-oauth.a
src/interfaces/libpq-oauth/libpq-oauth.a.p/oauth-curl.c.o && ranlib -c
src/interfaces/libpq-oauth/libpq-oauth.a
So it's getting -I/opt/local/include and also
-I/opt/local/libexec/openssl3/include from somewhere,
which I guess must be libcurl's pkg-config data ... yup:
$ pkg-config --cflags libcurl
-I/opt/local/include -I/opt/local/libexec/openssl3/include -I/opt/local/include
I bet Homebrew's libcurl packaging doesn't do that.
regards, tom lane
