Jim,

I don't think it's too verbose, but maybe you could delay it to the end of
the configure script so you don't have to either interrupt with control-C or
scroll back to see what went "wrong."

Here's another idea: Fail the flex test fairly silently (e.g. just "no"),
but fall back to a script that generates a nice, verbose error message
explaining the situation.  That way, when the user tries to call "make"
after modifying the .l file, the fake flex alternative script gets called,
displays the message, and exits with status 1.

Nick

Jim Gallacher wrote:
> Gregory (Grisha) Trubetskoy wrote:
> 
>
> I've made the changes to configure.in, but before I commit I wanted to
> get some feedback. Are the following configure messages unclear or too
> verbose?
>
> For the case of the missing flex, ./configure will generate:
> ...
> checking for --with-flex... no
> checking for flex... no
> configure: WARNING: flex  not found
>   You can generally ignore this warning unless you need to regenerate
>   psp_parser.c from psp_parse.l. If you do need regenerate psp_parser.c,
>   use --with-flex to specify the location of flex.
>   See the README for more information.
> ...
>
> For the case of the wrong flex version, ./configure will generate:
> ...
> checking for --with-flex... no
> checking for flex... /usr/local/sbin/flex
> found /usr/local/sbin/flex, we'll use this. Use --with-flex to specify
> another.
> checking flex version... configure: WARNING: Flex version 2.5.4 found.
>   Version 2.5.31 or greater is required.
>   You can generally ignore this warning unless you need to regenerate
>   psp_parser.c from psp_parse.l. If you do need regenerate psp_parser.c,
>   use --with-flex to specify the location of the correct flex version.
>   See the README for more information.
> ...
>
> Any comments?
>
> Jim

[ Post a follow-up to this message ]