| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: VS 2015 support in src/tools/msvc |
| Date: | 2016-03-08 15:43:23 |
| Message-ID: | 9775.1457451803@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Do we already have a hard dependency on perl for all non-Windows builds?
> I know it's been discussed but I don't recall. If so, back to what version?
I think the policy is we require perl for building from a git pull,
but not for building from a tarball. Thus, any files that perl is used
to produce have to be shipped in tarballs.
However, there definitely *is* a hard requirement on perl for Windows
builds, even from tarballs, and I thought this patch was only about
the Windows build?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-03-08 15:45:19 | Re: Odd warning from pg_dump |
| Previous Message | Tom Lane | 2016-03-08 15:36:51 | Odd warning from pg_dump |