Re: Removing obsolete configure checks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Removing obsolete configure checks
Date: 2022-07-23 04:05:31
Message-ID: 804996.1658549131@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Fri, Feb 21, 2020 at 7:00 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> All of the above are required by C99 and/or SUSv2, and the configure-using
>> buildfarm members are unanimous in reporting that they have them, and
>> msvc/Solution.pm expects Windows to have them.

> I think the same now applies to <wctype.h>, without gaur. So I
> propose the attached. I split it into two patches, because 0001 is
> based on scraping build farm configure output, while 0002 is an
> educated guess and might finish up needing to be reverted if I'm
> wrong.

+1. SUSv2 is perfectly clear that <wctype.h> is supposed to declare
these functions. I'm not surprised that gaur's 1996-ish system headers
failed to see into the future; but prairiedog is up to speed on this
point, and I should think all the surviving BF animals are too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-07-23 04:57:47 Re: Removing obsolete configure checks
Previous Message Julien Rouhaud 2022-07-23 04:03:34 Re: Expose Parallelism counters planned/execute in pg_stat_statements