| Jim Gallacher 2005-08-26, 5:46 pm |
| Nick wrote:
> 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."
Good point. I'll move it to the end. Since most systems still ship with
the older flex, most people that compile mod_python will see this message.
> 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.
My personal preference is to keep this sort of thing in configure. I
hate it when configure succeeds but then make fails. I'm more inclined
to leave the message in configure, but with the additional test you
suggest added just in case the .l file has changed.
Jim
> Nick
>
> Jim Gallacher wrote:
>
>
>
|