From: | Robert Creager <robert(at)logicalchaos(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_crypto failures with llvm on OSX |
Date: | 2012-03-11 01:07:14 |
Message-ID: | F2507FFD-0DDC-414A-8D3B-A39A15CEF54F@logicalchaos.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mar 10, 2012, at 5:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> What's really odd though is that there is nothing in the configuration
> script that injects any of those switches. I think you've got some
> screwy global configuration on that machine, which you'd be well advised
> to try to get rid of --- it's tough for people to do remote diagnosis of
> buildfarm critters when there's relevant configuration that's not
> exposed in the config script.
No global config. Changed the path around to have /opt/local after the standard Apple ones, and it appears to be working fine. autoconf must be throwing in that path based on executables found?
Later,
Rob
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-03-11 02:15:49 | Re: pg_crypto failures with llvm on OSX |
Previous Message | Tom Lane | 2012-03-11 00:01:55 | Re: pg_crypto failures with llvm on OSX |