Re: Issues while building PG in MS Windows, using MSYS2 and MinGW-w64

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "insaf(dot)k" <insaf(dot)k(at)zohocorp(dot)com>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issues while building PG in MS Windows, using MSYS2 and MinGW-w64
Date: 2018-04-27 15:31:56
Message-ID: 26745.1524843116@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"insaf.k" <insaf(dot)k(at)zohocorp(dot)com> writes:
> I am trying to build PG from source, in MS Windows using MSYS2 and MinGW-w64. I've tried to build PG 10.0 as wells as 10.3.
> I've done configuring like this
> ./configure --prefix="/d/pg10/"
> And when I do "make" or "make world", I'm getting compilation error. I've attached complete error report at the end of the mail.

I don't know anything about mingw, but from the first error message you
showed, I'd venture that configure failed to fill in pg_config_ext.h
correctly. It should have put in a line like

#define PG_INT64_TYPE long long int

and evidently it hasn't. This suggests that there's something wrong
with one of the text-processing tools it uses, such as "sed". You
might look into config.log and see if there are any relevant-looking
error messages (probably down near the end). Also, try comparing
your configure text output and config.log to those of one of our
buildfarm machines that's using mingw successfully, such as

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jacana&dt=2018-04-27%2012%3A19%3A49

(the "config" and "configure" links on that page are what to compare to).

Hm ... I notice that jacana's been set up so that it explicitly
gives configure a --host setting instead of letting configure work
that out. No idea if that was really necessary or not.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2018-04-27 15:33:31 Re: Built-in connection pooling
Previous Message Peter Eisentraut 2018-04-27 15:10:31 Re: obsoleting plpython2u and defaulting plpythonu to plpython3u