Re: pg_crypto failures with llvm on OSX

On Mar 10, 2012, at 7:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Robert Creager <robert(at)logicalchaos(dot)org> writes:
>> 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?
>
> I don't believe autoconf would insert such stuff on its own authority.
> I'm wondering about CPPFLAGS, CFLAGS, LDFLAGS or similar variables being
> set in the environment that the buildfarm script is running in.
> Take a look at ~/.bash_profile and suchlike files.

Nope. Only PATH is set.

Later,
Rob