On 29 April 2016 at 04:39, Adrien Destugues <pulkomandy@xxxxxxxxxxxxx> wrote:
I think this may just be an intermediate issue with certain versions of
flex. I saw it with 2.5.37
IIRC, but upgrading to 2.5.39 fixed it. Not sure which version Ubuntu
16.04 uses, but might be
worth checking.
I looked at it for a while but have 0 flex/bison/yacc knowledge and
couldn't figure out a better
solution.
Since this code is pretty core to our network stack, I disabled Werror
until someone with more
bison knowledge
could take a crack.
Feel free to fix more completely if you have the l33t bison skills :-)
You misunderstood me. You probably simply need to update flex on your host
machine to a version
that doesn't have this bug. 2.5.39 works for instance, 2.5.37 does not.
There's a version 2.6.0 as
well, but I haven't tried it beyond attempting to build it from the source
and being told that it
requires a newer auto tools version.
https://sourceforge.net/p/flex/bugs/140/
So yes, looks like a bug in Flex. I would rather require people to avoid the
broken version, then, instead of hacking around it (one more check to add to
our configure script, maybe).
