Re: renaming configure.in to configure.ac

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: renaming configure.in to configure.ac
Date: 2020-07-17 18:53:05
Message-ID: 20200717185305.q7erbn6d5bcqsqac@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2020-07-17 10:46:30 +0200, Peter Eisentraut wrote:
> Okay, let's take a look. Attached is a patch series.

Cool.

> One thing that's annoying is that the release notes claim that configure
> should now be faster, and some of the changes they have made should support
> that, but my (limited) testing doesn't bear that out. Most notably, the
> newly arisen test
>
> checking for g++ option to enable C++11 features... none needed
>
> takes approximately 10 seconds(!) on my machine (for one loop, since "none
> needed"; good luck if you need more than none).

Something got to be wrong here, no? I see that there's a surprisingly
large c++ program embedded for this test, but still, 10s?

It's not even clear why we're seeing this test at all? Is this now
always part of AC_PROG_CXX?

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-17 18:55:08 Re: Binary support for pgoutput plugin
Previous Message Dean Rasheed 2020-07-17 18:08:53 Re: NaN divided by zero should yield NaN