Greg Stark <[EMAIL PROTECTED]> writes:
> This patch adds an autoconf test to check for the new incompatible version of
> flex.
It seems unlikely that we should cause configure to reject all future
versions of flex... .31 may be broken but I think we should assume that
they'l fix it.
Tom Lane <[EMAIL PROTECTED]> writes:
> Greg Stark <[EMAIL PROTECTED]> writes:
> > This patch adds an autoconf test to check for the new incompatible version of
> > flex.
>
> It seems unlikely that we should cause configure to reject all future
> versions of flex... .31 may be broken but I think
Greg Stark <[EMAIL PROTECTED]> writes:
> I inquired about this problem elsewhere, it's not a bug, it's an API change.
> Until postgres "ports" to the new API it won't work with newer versions of
> Flex.
If their intent was to break things, why wasn't this called flex 3.0?
Or at least 2.6? Callin
