Yes, that was my conclusion too.
---
Tom Lane wrote:
> [ followup to old message ]
>
> Greg Stark <[EMAIL PROTECTED]> writes:
> > This patch adds an autoconf test to check for the new incompatible version of
> > flex.
>
>
[ followup to old message ]
Greg Stark <[EMAIL PROTECTED]> writes:
> This patch adds an autoconf test to check for the new incompatible version of
> flex.
Peter E. claims that CVS tip does work with flex 2.5.31 --- so we
shouldn't need this patch anymore.
regards, tom lan
Tom Lane <[EMAIL PROTECTED]> writes:
> 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 wa
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
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:
> 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.
This patch adds an autoconf test to check for the new incompatible version of
flex.
--- programs.m4.~1.12.~ 2003-05-06 19:33:52.0 -0400
+++ programs.m4 2003-07-04 20:45:47.0 -0400
@@ -30,6 +30,10 @@
pgac_broken_flex=$pgac_candidate
continue
fi
