Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.
Date: 2023-04-17 18:57:27
Message-ID: 08dd6053-deee-52e9-954b-eb69232905c9@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


On 2023-04-17 Mo 11:22, Tom Lane wrote:
> Further cleanup of autoconf output files for GSSAPI changes.
>
> Running autoheader was missed in f7431bca8. This is cosmetic since
> we aren't using these HAVE_ symbols, but let's get everything in
> sync while we're looking at this.
>
> Discussion:https://postgr.es/m/2422362.1681741814@sss.pgh.pa.us
>

I think this also needs a fix in src/tools/msvc/Solution.pm, see
<https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bowerbird&dt=2023-04-17%2016%3A30%3A03>

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-04-17 19:53:41 Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.
Previous Message Tom Lane 2023-04-17 18:22:34 pgsql: Avoid trying to write an empty WAL record in log_newpage_range()

Browse pgsql-hackers by date

  From Date Subject
Next Message Miroslav Bendik 2023-04-17 19:41:25 Re: Incremental sort for access method with ordered scan support (amcanorderbyop)
Previous Message Tom Lane 2023-04-17 18:33:38 Re: Move defaults toward ICU in 16?