|
|
Posted by James Calivar on 11/08/06 21:33
Hey, that worked! Thanks so much! I didn't have flex installed, but
even when I did install it, "lex" still didn't work, so I just did a
"alias lex="flex"" and it worked.
Sorry it took me a while to reply. I've been out of town and just got
back and chekced messages.
Thanks again,
James
Andy Hassall wrote:
> On 5 Nov 2006 19:10:50 -0800, "James Calivar" <amheiserbush@yahoo.com.au>
> wrote:
>
> >checking for flex... lex
>
> Suspicious - should say "flex" not "lex".
>
> >checking for yywrap in -ll... no
> >checking lex output file root... ./configure: line 3246: lex: command
> >not
> >found
> >configure: error: cannot find output from lex; giving up
>
> What do you get from the command "which lex"? Do you have a shell alias for
> "lex" - e.g. does "alias lex" show an existing alias?
>
> FYI this is what I get in the same environment:
>
> [...]
> checking for flex... flex
> checking for yywrap in -lfl... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> checking for working const... yes
> checking for flex version... 2.5.4 (ok)
> checking whether to force non-PIC code in shared modules... no
> checking for pthreads_cflags...
> checking for pthreads_lib...
>
> Configuring SAPI modules
> [... etc., continues as normal.]
>
> --
> Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
> http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Navigation:
[Reply to this message]
|