Re: -HEAD on FreeBSD 6-CURRENT build failures - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: -HEAD on FreeBSD 6-CURRENT build failures
Date
Msg-id 41FAA02A.90306@dunslane.net
Whole thread Raw
In response to Re: -HEAD on FreeBSD 6-CURRENT build failures  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: -HEAD on FreeBSD 6-CURRENT build failures
List pgsql-hackers

Tom Lane wrote:

>Darcy Buskermolen <darcy@wavefire.com> writes:
>  
>
>>There looks to be an issue with gram.y  as seen in the following 2 FreeBSD6 
>>boxen:
>>    
>>
>
>  
>
>>http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=herring&dt=2005-01-28%2018:33:43
>>http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=echidna&dt=2005-01-28%2018:30:01
>>    
>>
>
>The "issue" is that your make is broken: it's failed to regenerate
>gram.c from the recently updated gram.y.
>
>The impression I have gained from watching the build farm is that ccache
>is seriously unreliable --- the machines using it often show transient
>build failures that look like failure to update derived files.
>
>
>  
>

The way buildfarm works is that it should always run on a clean set of 
CVS files - i.e. there should no gram.c. We don't even bot6her with 
clean, distclean, maintainer-clean and friends - we simply copy the 
source directory tree for each run. The fact that Darcy's builds don't 
show a call to bison indicates to me that his source dir ( 
/buildfarm/pg-buildfarm/HEAD/pgsql ) might not be clean for some reason 
that is not clear to me.

Darcy, please blow that directory tree away and see if the situation 
recovers.

cheers

andrew


pgsql-hackers by date:

Previous
From: Matthias Schmidt
Date:
Subject: Re: Allow GRANT/REVOKE permissions to be applied to all schema objects with one command
Next
From: Josh Berkus
Date:
Subject: Re: [pgsql-hackers] Group-count estimation statistics