Re: pg_crypto failures with llvm on OSX

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 02:54:29
Message-ID: 4F5C13E5.1060304@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Creager 2012-03-11 03:01:33 Re: pg_crypto failures with llvm on OSX
Previous Message Robert Creager 2012-03-11 02:52:41 Re: pg_crypto failures with llvm on OSX