New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove BisonHeaderToC++.sed #1517
Conversation
We can do without it, and less is more?
I'm not sure we can do without this. I know I had problems which lead me to do this which may be related to older versions of Bison. Note that it works for 3.0.4 compared to 2.7. My experience is that Bison versions on old operating systems we support tend to be very old. I will need to check this on older OS versions we use here at Y!. Additionally the plan going forward for this is to remove all the parsing from TSConfig and have it depend on Lua. |
Thanks for taking a look! It should work with Bison 2.7, just based on the GitHub CI jobs (e.g. the FreeBSD job uses 2.7 [1]). The CentOS 6 machine uses 2.4 [2] -- but we don't run that for pull requests, I think. I think the important difference between TsConfigGrammar.h and TsConfigGrammar.hpp is that TsConfigGrammar.h contains yyscan_t (the first tsconfigparse() parameter) and TsConfigGrammar.hpp doesn't -- but replacing [1] https://ci.trafficserver.apache.org/files/BuildMachines/FreeBSD10
Nice! |
Lets re-run this with the new Github builders: [approve ci] |
Note that it has to succeed on CentOS6, which is indeed running
|
@jablko can you rebase this? |
[approve ci] |
Still feels like we have to support the Bison that comes with CentOS6. |
Ran a build on this for Centos 6 to see if there is an issue. |
Part of the "trickiness" here is that the file is also checked into git, so many cases, we don't need bison at all. But it doesn't seem to be particularly deterministic. |
There hasn't been an update on this PR for over 60 days, so I am closing it for now. Feel free to reopen the PR when you have updated it. |
We can do without it, and less is more?