Re: [HACKERS] build farm failures

2007-08-16 Thread Andrew Dunstan
Alvaro Herrera wrote: How do you create the copy of the repo to build? One idea would be to explicitely skip files that appear on .cvsignore (and maybe croak about them). We are supposed to croak - see http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.d

Re: [HACKERS] build farm failures

2007-08-16 Thread Alvaro Herrera
Andrew Dunstan wrote: > > > Michael Meskes wrote: >> The backend has: >> >> $(srcdir)/gram.c: $(srcdir)/parse.h ; >> >> $(srcdir)/parse.h: gram.y >> >> So except for the different naming it's the same. However, we haven't >> had that problem with the backend so far, or did we? >> >> What do I fail

Re: [HACKERS] build farm failures

2007-08-16 Thread Andrew Dunstan
Michael Meskes wrote: The backend has: $(srcdir)/gram.c: $(srcdir)/parse.h ; $(srcdir)/parse.h: gram.y So except for the different naming it's the same. However, we haven't had that problem with the backend so far, or did we? What do I fail to see? We have had problems in the past. If

Re: [HACKERS] build farm failures

2007-08-16 Thread Michael Meskes
On Thu, Aug 16, 2007 at 08:24:14AM -0700, Darcy Buskermolen wrote: > 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 assum

Re: [HACKERS] build farm failures

2007-08-16 Thread Andrew Dunstan
Alvaro Herrera wrote: Andrew Dunstan wrote: 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

Re: [HACKERS] build farm failures

2007-08-16 Thread Alvaro Herrera
Andrew Dunstan wrote: > > > 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 po

Re: [HACKERS] build farm failures

2007-08-16 Thread Darcy Buskermolen
On Thursday 16 August 2007 04:29:41 Andrew Dunstan wrote: > Michael Meskes wrote: > > Hi, > > > > we have two build farm members failing to make since I committed teh > > ecpg changes: echidna and herring. > > > > It looks like they are still using an old preproc.c although they > > checked out the

Re: [HACKERS] build farm failures

2007-08-16 Thread Andrew Dunstan
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 a

Re: [HACKERS] build farm failures

2007-08-16 Thread Andrew Dunstan
Michael Meskes wrote: Hi, we have two build farm members failing to make since I committed teh ecpg changes: echidna and herring. It looks like they are still using an old preproc.c although they checked out the new preproc.y. I have no idea how this is supposed to work so could someone pleas

[HACKERS] build farm failures

2007-08-16 Thread Michael Meskes
Hi, we have two build farm members failing to make since I committed teh ecpg changes: echidna and herring. It looks like they are still using an old preproc.c although they checked out the new preproc.y. I have no idea how this is supposed to work so could someone please enlighten me? Michael -