Help with elkhound port development

[Mark Brethen]

On Dec 12, 2014, at 9:28 PM, Brandon Allbery <allbery.b at gmail.com> wrote:

> I already answered this one: the program makes an assumption about how much of the bison header it needs to take, one which is incorrect for bison 3 as is currently in MacPorts and is also probably wrong for all bison 2 versions. (Note that bison since version 2 supports GLR parsers, suggesting that elkhound expects bison 1.x. However, it's almost certainly not going to be a drop-in replacement for elkhound.)
> 
> You are going to have to do some work to figure out how to adapt elkhound to bison 3, possibly by digging out a copy of bison 1.x somewhere and comparing the agrampar.tab.h it produces to the one bison 3 produces in order to find out what to replace the "head -n 73" with something that works to extract the appropriate token definitions from a bison 3-generated agrampar.tab.h.

I did find out from someone @weidu.org that the most recent version of bison known to be compatible is 2.5.

Mark