Re: PSA: Autoconf has risen from the dead - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PSA: Autoconf has risen from the dead
Date
Msg-id 20220705191420.auyzbkev2z7ffkh5@awork3.anarazel.de
Whole thread Raw
In response to Re: PSA: Autoconf has risen from the dead  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2022-07-05 15:06:31 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > Yea. They might not be independent of where you get other dependencies from
> > though. Does macports install headers / libraries into a path that's found by
> > default? Or does one have to pass --with-includes / --with-libs to configure
> > and set PKG_CONFIG_PATH, like with homebrew?
> 
> What are you expecting to need PKG_CONFIG_PATH for?  Or more precisely,
> why would meson/ninja create any new need for that that doesn't exist
> in the autoconf case?

It's just used in more cases than before, with fallback to non-pkg-config in
most cases. I think all dependencies besides perl can use pkg-config. So all
that changes compared to AC is that you might not need to pass extra
include/lib paths for some dependencies that needed it before, if you set/pass
PKG_CONFIG_PATH.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Next
From: Tom Lane
Date:
Subject: Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load