Tom Lane wrote: > Markus Bertheau <[EMAIL PROTECTED]> writes: > >> what version of bison are you using? I believe we require 1.875 these days. > > > 1.35. I'll upgrade. Thanks. > > I believe 'configure' will bleat about a too-old bison, but it won't > refuse to proceed --- and the warning is easy to miss in the pages of > output that configure produces. > > I was against having configure error out if bison is too old, since > you might not need it at all (if building from a tarball). But it > seems like we still have the problem. > > Maybe make configure act as though bison is missing? Not sure. It > seems like that could create unnecessary problems in other cases.
One trick would be to set YACC to some special value like "bison.too.old" and test for that when YACC is actually called from the Makefile. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
