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 co
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 anyth
Andrew Dunstan 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
Robert Creager writes:
> On Mar 10, 2012, at 7:15 PM, Tom Lane wrote:
>> 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
On Mar 10, 2012, at 7:54 PM, Andrew Dunstan wrote:
>
>
> 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
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 th
On Mar 10, 2012, at 7:15 PM, Tom Lane wrote:
> Robert Creager writes:
>> On Mar 10, 2012, at 5:01 PM, Tom Lane 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 configurati
Robert Creager writes:
> On Mar 10, 2012, at 5:01 PM, Tom Lane 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
On Mar 10, 2012, at 5:01 PM, Tom Lane 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 t
Robert Creager writes:
> On Mar 10, 2012, at 4:19 PM, Andrew Dunstan wrote:
>> On 03/09/2012 07:50 PM, Tom Lane wrote:
>>> I suspect that mussel has an ABI-incompatible openssl library hanging
>>> around someplace. On my machine "otool -L pgcrypto.so" shows
>>> /usr/lib/libcrypto.0.9.8.dylib (co
On Mar 10, 2012, at 4:19 PM, Andrew Dunstan wrote:
>
> On 03/09/2012 07:50 PM, Tom Lane wrote:
>> Andrew Dunstan writes:
>>> Buildfarm member mussel (OS X 10.7.3, llvm-gcc 4.2.1, x86_64)seems to be
>>> getting consistent warnings when running the pgcrypto regression tests,
>>> that look like th
On 03/09/2012 07:50 PM, Tom Lane wrote:
Andrew Dunstan writes:
Buildfarm member mussel (OS X 10.7.3, llvm-gcc 4.2.1, x86_64)seems to be
getting consistent warnings when running the pgcrypto regression tests,
that look like this:
WARNING: detected write past chunk end in ExprContext 0x7fe
Andrew Dunstan writes:
> Buildfarm member mussel (OS X 10.7.3, llvm-gcc 4.2.1, x86_64)seems to be
> getting consistent warnings when running the pgcrypto regression tests,
> that look like this:
> WARNING: detected write past chunk end in ExprContext 0x7fec2b11eb58
> Does anyone have an id
On Fri, Mar 09, 2012 at 05:28:20PM -0500, Andrew Dunstan wrote:
> Buildfarm member mussel (OS X 10.7.3, llvm-gcc 4.2.1, x86_64)seems
> to be getting consistent warnings when running the pgcrypto
> regression tests, that look like this:
>
>WARNING: detected write past chunk end in ExprContext 0
Buildfarm member mussel (OS X 10.7.3, llvm-gcc 4.2.1, x86_64)seems to be
getting consistent warnings when running the pgcrypto regression tests,
that look like this:
WARNING: detected write past chunk end in ExprContext 0x7fec2b11eb58
Does anyone have an idea why that might be?
cheers
and
15 matches
Mail list logo
