On Sun, Nov 13, 2005 at 10:45:32PM +0100, Leopold Toetsch wrote: > ... which has bison 1.28 installed (not quite state of the art) > > *) tried apt-cache search bison > - most recent package reported is 1.35 - that's ancient too > - canceled
I started a thread about this a couple of weeks ago. I really think that bison 1.75c should be the minimum requirement. > Now parrot: > > *) perl Configure --yacc=~/bison/bin/bison > > - ERR - the --yacc option doesn't automagically select --maintainer > - TODO just use it, if --yacc is given (same with --lex) Fixed in r9953. > *) perl Configure --yacc=~/bison/bin/bison --maintainer > > - Configure now selects my new shiny bison > - ERR during make: > ~/bison/bin/bison imcc/imcc.y -d -o imcc/imcparser.c > make: ~/bison/bin/bison: Command not found > - TODO err early about relative file paths or make it work I don't feel that this is a bug. The old logic was to check if the user supplied bison exists and if not to search for it. The new logic is if the user specified it they get it. To do anything else would be like silently overriding the value of CC. > *) perl Configure --yacc=/Users/lt/bison/bin/bison --maintainer > > - make works finally imcc.y, ast.y are compiled w/o any complaint > > *) make test > - shows the expected 5 test errors [1] caused by s/parser > error/syntax error/ > - TODO allow both spellings in test result This is the same problem as supporting bison < 1.75c & bison >= 1.75c. If anyone writes down stream tests that depend on Parrot's error strings, having flip flopping error strings is going to cause a support problem. We should either: a) decide what revisions of bison are supported or b) hard code all error strings Cheers, -J --
pgp13cXGQvpnv.pgp
Description: PGP signature
