Re: cvs build failure
От | Andrew Dunstan |
---|---|
Тема | Re: cvs build failure |
Дата | |
Msg-id | 003c01c3402e$31fe2b80$6401a8c0@DUNSLANE обсуждение исходный текст |
Ответ на | Re: cvs build failure (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-hackers |
Is it not possible to check when configure is run for the presence of the bison output files, and only fail if one or more is absent and the bison version is too low? just a thought. andrew ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Bruce Momjian" <pgman@candle.pha.pa.us> Cc: "Markus Bertheau" <twanger@bluetwanger.de>; "Larry Rosenman" <ler@lerctr.org>; <pgsql-hackers@postgresql.org> Sent: Tuesday, July 01, 2003 7:10 PM Subject: Re: [HACKERS] cvs build failure > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > I can see making a new bison required only when the version is *devel. > > That way, folks testing CVS and even the *devel snapshots would need a > > new bison, but our normal users wouldn't. > > Even then, if they're using a snapshot they shouldn't need it. > > Perhaps a combination of your idea and Alvaro's: set things up so that > we fail only when bison is actually invoked by the makefiles, plus > provide a way to override the version check if it's wrong. > > regards, tom lane >
В списке pgsql-hackers по дате отправления: