Re: Bug #2366: No Bison

Oh man, you are right. parsedate.y was added, but we forgot to add a rule to our distribution building tool to auto-generate parsedate.c from it. I have fixed this now and 3.0.13 will definitely have it. On Thu, 23 Sep 1999, Don Rude wrote: > Rasmus Lerdorf wrote: > > > > Are you actually getting an error? The most you should get if you don't > > have Bison installed is a warning. > > > I get both the configure 'warning' and then during make it stops saying that > Bison could not be found (since it's not installed). Here are the './configure' > and 'make' warnings. > > > configure: warning: You will need bison if you'd want to regenerate the PHP 3.0 > parsers. > > bison -v -d ./functions/parsedate.y -o functions/parsedate.c > make: bison: Command not found > make: *** [functions/parsedate.c] Error 127 > > > I just generated these by doing a standard configure/make on my dev server > (after removing Bison since our successful compile last night) but we had the > same behavior yesterday using our standard recompile routine. > > The 'standard recompile' also adds in mod_ssl and links PHP against mySQL and > cybercash MCK. If you would like my full config info I'll gladly share it but > this little re-test I did just now to generate the above text seems to show my > config has little to do with it. Not to mention that I have done this same > series of steps many times in the past with no bison trouble. > > Thanks for the prompt response. I'm CC-ing John Barrett who posted bug 2002 > since he will also be interested in the outcome of this 'bug'. > > >