Ari Johnson schreef: > On Thu, Jun 12, 2008 at 11:58 PM, bugs buggy <[EMAIL PROTECTED]> wrote: >> You wouldn't happen to know what causes (or caused) this would you: >> bison\ -y\ -d\ -o\"${INPUT_FILE_BASE}\".tab.h\ \"${INPUT_FILE_PATH}\"\ >> ||\ exit\ 1 >> bison\ -y\ -d\ -o\"${INPUT_FILE_BASE}\".tab.c\ \"${INPUT_FILE_PATH}\"\ >> ||\ exit\ 1 >> /Users/thommy/2.1/macosx/../lib/framework/resource_parser.y:51: >> unrecognized: %name_prefix >> /Users/thommy/2.1/macosx/../lib/framework/resource_parser.y:51: >> Skipping to next % >> /Users/thommy/2.1/macosx/../lib/framework/resource_parser.y:61: >> unrecognized: %destructor >> /Users/thommy/2.1/macosx/../lib/framework/resource_parser.y:61: >> Skipping to next % >> ** BUILD FAILED ** >> >> Or is that now fixed? >> It seems weird it sees %name_prefix, and not %name-prefix. > > That was caused by someone changing our .y files to require a version > of Bison newer than the one included with OS X.
Those changes could explain the error on line 61 (%destructor), but they don't explain the error on line 51. Line 51 holds the %name-prefix directive, which we've used since the dawn of days... PS That someone is me. I changed several parsers (.y files) to use the %destructor feature, which is only available without being seriously broken in Bison > 2.1. -- Giel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev