Re: build farm failures - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: build farm failures
Date
Msg-id 46C47752.1070500@dunslane.net
Whole thread Raw
In response to build farm failures  (Michael Meskes <meskes@postgresql.org>)
Responses Re: build farm failures  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers

Darcy Buskermolen wrote:
>> This sort of thing is usually a
>> symptom of somebody having run a build in the repo directly, a thing
>> that buildfarm owners have been repeatedly advised not to do.
>>     
>
> This is something I do not recall doing, however it's possible.  though this 
> does make me ask why are the build dependencies in the Makefile are not 
> properly setup to tell that the .y needs to be rebuilt (which I would assume 
> would make this problem also go away)
>
>   

Thje way cvs works is that it gives the file the date it has in the 
repository, so if your preproc.c is newer than the preproc.y, make will 
detect that and not rebuild it.  If Michael's checkin occurs between the 
time the repo is updated and the time bison gets run on the original 
file this will happen. But if you never ever build in the repo then it 
won't, because buildfarm only ever builds in a copy (unless you're 
building with vpath, in which case it cleans up the generated files).

cheers

andrew


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: tsearch2 in PostgreSQL 8.3?
Next
From: Tom Lane
Date:
Subject: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)