Your message dated Thu, 29 Nov 2018 20:20:34 -0800 with message-id <CAJjFYLYn-dxnTG_UEXLXGKks6GReOBfM0Ckc1xnbgAKMeuXy=a...@mail.gmail.com> and subject line Closing #689700 has caused the Debian Bug report #689700, regarding bison: generate incompatible header file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 689700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689700 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bison Version: 1:2.6.2.dfsg-1 Severity: normal Hello Chuan-kai, This version of bison -d parse.y generates a parse.h ending file with the following (assuming the file contain %parse-param {char **lex} ) #ifdef YYPARSE_PARAM #if defined __STDC__ || defined __cplusplus int parse (void *YYPARSE_PARAM); #else int parse (); #endif #else /* ! YYPARSE_PARAM */ #if defined __STDC__ || defined __cplusplus int parse (char **lex); #else int parse (); #endif This was not done in bison 2.4.1 and earlier release, and as far as I can see this change is not documented anywere. This is unfortunate because this does not necessarily declare int parse (char **lex) in the right C++ namespace, causing conflict with the user supplied prototype (which is certainly necessary with older releases), causing compilation error. Cheers, -- Bill. <[email protected]> Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---This bug was opened over 6 years ago, and regardless of whether the bison package was at fault, it is likely that all affected software would have made changes to accommodate the incompatible header file. So I am marking this bug as done. Chuan-kai Lin
--- End Message ---
