From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
cc: pgsql-hackers@postgresql.org
Subject: Re: PL_stashcache, or, what's our minimum Perl version?
In-reply-to: <a597cbfe-c214-1313-950d-3f8a8173e950@2ndQuadrant.com>
References: <20540.1501210115@sss.pgh.pa.us> <24665.1501214288@sss.pgh.pa.us>
 <fd90cca4-db1c-b760-dd17-eafa304020d6@2ndQuadrant.com>
 <a597cbfe-c214-1313-950d-3f8a8173e950@2ndQuadrant.com>
Comments: In-reply-to Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
	message dated "Fri, 28 Jul 2017 15:01:11 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4038.1501277046.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 Jul 2017 17:24:06 -0400
Message-ID: <4039.1501277046@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> On 07/27/2017 11:58 PM, Tom Lane wrote:
>>> I wonder if it'd be worth getting the buildfarm
>>> to log the output of "perl -V" so we could get a clearer picture
>>> of what's being tested.

> Looks like this, bit it's rather tedious. I think I might back it out. I
> guess I could also write it to a log file, if we really think we need it.
> <https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dcrake&dt=3D201=
7-07-28%2018%3A37%3A19>

Yeah, that's awfully verbose :-(.  I suspect most vendors wouldn't bother
with enumerating quite so many patches.

I fixed configure so that it will report what it saw in $Config{ccflags};
that may be sufficient.

			regards, tom lane


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers