vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| There looks to be an issue with gram.y as seen in the following 2 FreeBSD6 boxen: http://pgbuildfarm.org/cgi-bin/show_...-28%2018:33:43 http://pgbuildfarm.org/cgi-bin/show_...-28%2018:30:01 -- Darcy Buskermolen Wavefire Technologies Corp. ph: 250.717.0200 fx: 250.763.1759 http://www.wavefire.com ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
| ||||
| Andrew Dunstan <andrew@dunslane.net> writes: > 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. Hmm, source directory used for a build and then not maintainer-clean'd perhaps? If you do the copy without -p then the copy would tend to lose the timestamps that would show that the gram.c file is out of date. I suppose "cp -p" would be a bad idea because of permissions issues, but you could consider replacing the cp with "tar cf - | tar xf -" to preserve timestamps better. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org |
| Thread Tools | |
| Display Modes | |
|
|