-
Notifications
You must be signed in to change notification settings - Fork 537
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bison includes its generated header in *.cc. Generate with correct name.
The current bison (3.7) generates a *.cc file that includes the header it generated. For parse.cc this would be parse.hh. Right now, we rename this header to have a common name used in other files, but this results in a compile error for the parse.cc file: parse.cc:462:10: fatal error: parse.hh: No such file or directory 462 | #include "parse.hh" | ^~~~~~~~~~ Fix this by telling bison to output the header file to the correct filename in the first place so that we don't have to rename it. (using the --defines instead of -d option). This looks like a bison specific option not available in Posix yacc; but looks like we're requiring bison anyway. Signed-off-by: Henner Zeller <h.zeller@acm.org>
- Loading branch information
Showing
4 changed files
with
4 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters