Re: buildfarm build failure: icc7 + --enable-cassert

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <peter_e(at)gmx(dot)net>, <darcy(at)wavefire(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: buildfarm build failure: icc7 + --enable-cassert
Date: 2004-12-12 22:06:16
Message-ID: 2110.24.211.141.25.1102889176.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane said:
> "Andrew Dunstan" <andrew(at)dunslane(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>
>> Maybe we need to look at some rpath settings?
>
> Or PATH. If I'm reading the direction of conflict correctly, the
> out-of-date component is the postgres executable, not the .so file.
>
> Why does the page appear to show /buildfarm/bin at the end of PATH?
> Shouldn't it be at the beginning?
>

I don't see why it's there at all - buildfarm didn't put it there unless
Darcy added something to the config file. The canonical member of buildfarm
is dog, which is an FC1 box run by me, and which runs with the path cron
gives it, namely /usr/bin:/bin - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dog&dt=2004-12-12%2019:06:01
In any case, I doubt it has anything but the script and config file. It
can't be the build installdir, because that always includes the cvs branch
name (e.g. HEAD).

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-12-12 22:08:08 Re: [Testperf-general] BufferSync and bgwriter
Previous Message Marc G. Fournier 2004-12-12 19:53:51 Re: Anonymous CVS not updating?