From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Robert Creager <robert(at)logicalchaos(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_crypto failures with llvm on OSX |
Date: | 2012-03-11 05:34:15 |
Message-ID: | 14683.1331444055@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:
> On 03/10/2012 09:15 PM, Tom Lane wrote:
>> (I wonder whether it'd be a good idea for the buildfarm script to
>> explicitly clear anything that autoconf pays attention to from its
>> startup environment, so that you have to set these variables in the
>> buildfarm config to make them have effect. If not that, maybe print
>> "env" output to document what the situation is?)
> I can put the latter in the next client release, unless people think
> it's a bit insecure to report arbitrary environment values. If we were
> to clear them, which would we clear?
I think it'd be useful to print CPPFLAGS, CFLAGS, and LDFLAGS if the
environment is supplying values for them (or maybe print their values
after absorbing whatever is in the buildfarm animal's config).
Peter might know whether there's anything else of great interest.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2012-03-11 10:25:01 | ecpg.sgml: the the -> the |
Previous Message | Tom Lane | 2012-03-11 05:32:20 | Re: pg_crypto failures with llvm on OSX |