From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Darcy Buskermolen <darcy(at)wavefire(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: buildfarm build failure: icc7 + --enable-cassert |
Date: | 2004-12-12 19:05:31 |
Message-ID: | 7256.1102878331@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Darcy Buskermolen wrote:
>> It looks like --enable-cassert isn't handled properly under icc7
>>
>> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=herring&dt=2004-12-07%2016:30:44
> That is quite a superficial display of the issue. If you want to get to
> the bottom of this, you need to, uh, dig deeper.
This looks to me like a standard incompatible-version-of-shared-library
issue, specifically, the .so was built with --enable-cassert but the
backend trying to load it was not. Andrew claims he's designed the
buildfarm test sequence to prevent that sort of problem (by deleting the
previous installation before doing "make check") but I think he musta
missed something.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-12-12 19:25:03 | Re: buildfarm build failure: icc7 + --enable-cassert |
Previous Message | Travis P | 2004-12-12 19:01:26 | Re: Call for port reports |