Re: configure.in: Look for flex

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Kevin Ryde <[EMAIL PROTECTED]> writes: > >> If the generated file is checked into the cvs and the dates are right >> then you won't need flex for a maintainer build, unless you actually >> change the source. > > Actually I needed it, hence this thread.

Re: configure.in: Look for flex

Kevin Ryde <[EMAIL PROTECTED]> writes: > If the generated file is checked into the cvs and the dates are right > then you won't need flex for a maintainer build, unless you actually > change the source. Actually I needed it, hence this thread. ;-) `AM_PROG_FLEX' is probably the right thing, yes

Re: configure.in: Look for flex

[EMAIL PROTECTED] (Ludovic Courtès) writes: > > Since flex is needed when building from CVS and not needed when building > from a distribution, what about something like the following: I think AM_PROG_LEX probably does everything you need, with no explicit warning code needed. It looks like it se

Re: configure.in: Look for flex

Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > No, this shouldn't be an error. The dist includes the generated C > code so you don't need lex in a normal build. > > (You need lex if you change the ".l", and in a maintainer build maybe, > so a configure check is good, but it shouldn't be an error.)

Re: configure.in: Look for flex

Rob Browning <[EMAIL PROTECTED]> writes: > > flex --version || ... Or the "missing" script, maybe, if autoconf/automake doesn't already set that up. > What would the configure check actually get us? Only allowing the system lex instead of insisting on flex, I think. (Which may or may not

Re: configure.in: Look for flex

Kevin Ryde <[EMAIL PROTECTED]> writes: > (You need lex if you change the ".l", and in a maintainer build maybe, > so a configure check is good, but it shouldn't be an error.) Or, we might just add a test with a suitable error message to the make rule that uses flex... flex --version || .

Re: configure.in: Look for flex

[EMAIL PROTECTED] (Ludovic Courtès) writes: > > + AC_MSG_ERROR([flex not found. See README.]) No, this shouldn't be an error. The dist includes the generated C code so you don't need lex in a normal build. (You need lex if you change the ".l", and in a maintainer build maybe, so a configure ch

configure.in: Look for flex

Hi, The following change updates `README' and `configure.in' so that they mention flex. Thanks, Ludovic. 2005-06-16 Ludovic Courtès <[EMAIL PROTECTED]> * configure.in: Look for `flex'. * README: Mention flex as a require