On 16.07.22 17:26, Tom Lane wrote:
On the whole though, my feeling is that autoconf 2.71 doesn't
offer enough to us to justify possibly causing substantial pain
for a few developers. I recommend setting this project aside
for now. We can always reconsider if the situation changes.
Ok, let's d
... anyway, to get back to the main point of this thread:
The Autoconf developers were pretty responsive to my bug reports,
and after some back-and-forth we determined that:
1. The minimum GNU m4 version for modern autoconf is 1.4.8; this
is directly traceable to intentional behavioral changes in
On Tue, Jul 5, 2022 at 3:02 PM Andres Freund wrote:
> 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
Hi,
On 2022-07-05 15:06:31 -0400, Tom Lane wrote:
> Andres Freund 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 /
Andres Freund 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 ho
Hi,
On 2022-07-05 14:52:05 -0400, Tom Lane wrote:
> I dunno anything about the other steps Andres mentioned, but
> presumably they're independent of where you got meson from.
Yea. They might not be independent of where you get other dependencies from
though. Does macports install headers / librar
On Tue, Jul 5, 2022 at 2:52 PM Tom Lane wrote:
> Andres Freund writes:
> > On 2022-07-05 14:42:03 -0400, Robert Haas wrote:
> >> Since I'm a macports user I hope at some point we'll have directions
> >> for that as well as for homebrew.
>
> > But it looks like it's just
> > sudo port install me
Andres Freund writes:
> On 2022-07-05 14:42:03 -0400, Robert Haas wrote:
>> Since I'm a macports user I hope at some point we'll have directions
>> for that as well as for homebrew.
> But it looks like it's just
> sudo port install meson
Yeah, that's what I did to install it locally. The ninj
Hi,
On 2022-07-05 14:42:03 -0400, Robert Haas wrote:
> On Sun, Jul 3, 2022 at 1:17 PM Andres Freund wrote:
> > Yea, I guess I should start a documentation section...
> >
> > I've only used homebrew on mac, but with that it should be something along
> > the
> > lines of
> >
> > brew install meson
On Sun, Jul 3, 2022 at 1:17 PM Andres Freund wrote:
> Yea, I guess I should start a documentation section...
>
> I've only used homebrew on mac, but with that it should be something along the
> lines of
>
> brew install meson
> meson setup --buildtype debug -Dcassert=true build-directory
> cd buil
Hi,
On 2022-07-03 10:50:49 -0400, Tom Lane wrote:
> Robert Haas writes:
> > Hmm, I also don't know how annoying it's going to be to get the new
> > ninja/meson stuff working on macOS ... I really hope someone puts a
> > good set of directions on the wiki or in the documentation or
> > someplace.
Robert Haas writes:
> Hmm, I also don't know how annoying it's going to be to get the new
> ninja/meson stuff working on macOS ... I really hope someone puts a
> good set of directions on the wiki or in the documentation or
> someplace.
If you use MacPorts it's just "install those packages", and
On Sat, Jul 2, 2022 at 1:42 PM Tom Lane wrote:
> On the whole, I'm questioning the value of messing with our autoconf
> infrastructure at this stage. We did agree at PGCon that we'd keep
> it going for a couple years more, but it's not real clear to me why
> we can't limp along with 2.69 until we
I wrote:
> So that explains part of it: most of the failures are down to using
> Apple's hoary m4 instead of the one from MacPorts. We could usefully
> warn about that in our own docs, perhaps.
Hmm. I have just spent a very frustrating hour trying, and failing,
to build any version of GNU m4 fro
Peter Eisentraut writes:
> To summarize:
> - Autoconf 2.71 has been out for 1.5 years.
> - It is available in many recently updated OSs.
> - It allows us to throw away several workarounds.
> Hence:
>> Currently, I think early PG16 might be good time to do this update.
In preparation for reviewing
On 24.01.22 09:11, Peter Eisentraut wrote:
On 23.01.22 17:29, Tom Lane wrote:
While chasing something else, I was surprised to learn that the
Autoconf project has started to make releases again. There are
2.70 (2020-12-08) and 2.71 (2021-01-28) versions available at
https://ftp.gnu.org/gnu/auto
On 24.01.22 15:14, Tom Lane wrote:
Do these versions fix any bugs that affect us (i.e., that we've
not already created workarounds for)?
The only thing that could be of interest is that the workaround we are
carrying in config/check_decls.m4 was originally upstreamed by Noah, but
was then lat
Peter Eisentraut writes:
> I have patches ready for this at
> https://github.com/petere/postgresql/tree/autoconf-updates.
> My thinking was to wait until Autoconf 2.71 has trickled down into the
> OS versions that developers are likely to use.
I find that kind of irrelevant, because we expect p
Hi,
On 2022-01-23 11:29:17 -0500, Tom Lane wrote:
> Right now, I'm not sure we care; there seems to be more
> enthusiasm for switching to meson. But if that idea falls
> through, we should update to a newer autoconf release.
Depending on the number of portability fixes in those releases the
back
On 23.01.22 17:29, Tom Lane wrote:
While chasing something else, I was surprised to learn that the
Autoconf project has started to make releases again. There are
2.70 (2020-12-08) and 2.71 (2021-01-28) versions available at
https://ftp.gnu.org/gnu/autoconf/
I have patches ready for this at
ht
"Joel Jacobson" writes:
> I don't have much experience in this area, but I noted there is
> an AC_CACHE_SAVE feature to speed up rerunning ./configure,
> necessary when it stops with an error due to some missing dependency.
> Is there a good reason why AC_CACHE_SAVE is not used?
Dunno ... it look
On Sun, Jan 23, 2022, at 17:29, Tom Lane wrote:
>While chasing something else, I was surprised to learn that the
>Autoconf project has started to make releases again. There are
>2.70 (2020-12-08) and 2.71 (2021-01-28) versions available at
>https://ftp.gnu.org/gnu/autoconf/
>
>Right now, I'm not s
22 matches
Mail list logo
