Re: Compilation errors with mingw build caused by undefined optreset

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Compilation errors with mingw build caused by undefined optreset
Date: 2014-05-08 23:51:52
Message-ID: CAB7nPqT+ZO7C05KCmk3bGicFUB3p0M7B=cAZZinUq2-CKnWAYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 9, 2014 at 12:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> Since commit 60ff2fd introducing the centralizated getopt-related
>> things in a global header file, build on Windows with mingw is failing
>
> Hm, buildfarm member narwhal doesn't seem to be having any such problem.
> (It's got its own issues, but not this.)
>
> Do you think you could put up a buildfarm critter using whatever version
> of mingw you're using? Without buildfarm feedback, things *will* break
> regularly; Windows is just too weird to expect otherwise.
Yeah, after sleeping on this I had the same thought. I'll try to get
one working properly.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-05-08 23:56:30 Re: popen and pclose redefinitions causing many warning in Windows build
Previous Message Michael Paquier 2014-05-08 23:50:08 Re: Compilation errors with mingw build caused by undefined optreset