Re: Cygwin cleanup

Justin Pryzby <pryzby@telsasoft.com>

From: Justin Pryzby <pryzby@telsasoft.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org, Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>
Date: 2022-11-09T01:04:37Z
Lists: pgsql-hackers

Attachments

On Thu, Oct 20, 2022 at 10:40:40PM -0500, Justin Pryzby wrote:
> On Thu, Aug 04, 2022 at 04:16:06PM +1200, Thomas Munro wrote:
> > On Thu, Aug 4, 2022 at 3:38 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > > [train wreck]
> > 
> > Oh my, so I'm getting the impression we might actually be totally
> > unstable on Cygwin.  Which surprises me because ... wait a minute ...
> > lorikeet isn't even running most of the tests.  So... we don't really
> > know the degree to which any of this works at all?
> 
> Right.
> 
> Maybe it's of limited interest, but ..
> 
> This updates the patch to build and test with meson.
> Which first requires patching some meson.builds.
> I guess that's needed for some current BF members, too.
> Unfortunately, ccache+PCH causes gcc to crash :(

Resending with the 'only-if' line commented (doh).
And some fixes to 001 as Andres pointed out by on other thread.

-- 
Justin

Commits

  1. Use unnamed POSIX semaphores on Cygwin.

  2. meson: Basic cygwin support

  3. meson: Mark PROVE as not required