| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 13:19:34 |
| Message-ID: | 4F5CA666.4000805@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/11/2012 08:00 AM, Peter Eisentraut wrote:
> On sön, 2012-03-11 at 00:34 -0500, Tom Lane wrote:
>> 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.
> The ones that we have designated as pertinent are listed at the bottom
> of configure --help.
>
> But you can actually see the values that these had in the environment by
> looking in config.log under ac_cv_env_*.
Yeah, so there's nothing really to do here. And in the case of the
failures we saw, nothing was set, so Tom's analysis of the failure
coming from Macports libxml2 looks correct.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hunger | 2012-03-11 14:17:59 | Typo patch |
| Previous Message | Peter Eisentraut | 2012-03-11 12:00:04 | Re: pg_crypto failures with llvm on OSX |