Re: pg_crypto failures with llvm on OSX - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_crypto failures with llvm on OSX
Date
Msg-id 14683.1331444055@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_crypto failures with llvm on OSX  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_crypto failures with llvm on OSX  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_crypto failures with llvm on OSX
Next
From: "Erik Rijkers"
Date:
Subject: ecpg.sgml: the the -> the