[Webkit-unassigned] [Bug 20253] A correct Webkit build requires flex 2.5.33 but autotools build doesn't check for it

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Aug 2 01:40:29 PDT 2008


------- Comment #8 from zuh at iki.fi  2008-08-02 01:40 PDT -------
(In reply to comment #7)
> (From update of attachment 22615 [edit])
> Won't this check break with Flex 2.6?  Geez autoconf syntax sucks.

Well, it's more the tools that don't provide any way to check their version in
a sensible way than autoconf itself being broken, but the situation sucks

> This patch would make our behavior with Flex 2.6 worse than our current
> behavior.

Future-proofing the test would mean testing the major/minor/micro numbers
separately and hence the original more complex version. :)

Note that I wouldn't hold my breath for a 2.6 release as flex has really been
in the 2.5 series for over 10 (maybe even 15) years. I would imagine 2.6 would
require incompatible changes to be introduced, and thus the check would need to
exclude it anyway.

I don't care that much how the check is formulated, but I just want to prevent
people running into this very sneaky problem.

So, what should we do? Bring back the uglier, but future-proof version or..?

I'm not familiar with the actual usage of flex, maybe there's some way to check
for version at build time?

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list