Github user jablko commented on the issue:
https://github.com/apache/trafficserver/pull/1517
> 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!.
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
`%parse-param { yyscan_t lexer }` with `%parse-param { void *lexer }` has the
same effect?
[1] https://ci.trafficserver.apache.org/files/BuildMachines/FreeBSD10
[2] https://ci.trafficserver.apache.org/files/BuildMachines/CentOS6
> Additionally the plan going forward for this is to remove all the parsing
from TSConfig and have it depend on Lua.
Nice!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
