Re: Flex c++ bug

2003-02-04 Thread Aidan Delaney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 February 2003 20:21, Alexandre Duret-Lutz wrote: > > Automake 1.7.3 will have the following paragraphs in its manual. > [...] May I also suggest a note to say that AM_LFLAGS should be set to -olex.yy.c when building lexers with %option c

Re: Flex c++ bug

2003-02-04 Thread Alexandre Duret-Lutz
>>> "Aidan" == Aidan Delaney <[EMAIL PROTECTED]> writes: Aidan> balor@navi traditional $ make Aidan> flex traditional.ll && mv lex.yy.c traditional.cc Automake indeed does not support C++ scanners (i.e., flex -+), but will compile a C scanner as C++ source when asked so. [...] Aidan> AFAIK

Re: Flex c++ bug

2003-02-04 Thread Aidan Delaney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > Automake does not seem to differenciate between flex generated c++ files > > and c files > > Not if it has to guess. Use .ll or .l++ as the extension for your lex > file, drop the -+ and watch it work. :-) > > Reason behind that: automake needs to

Re: Flex c++ bug

2003-02-04 Thread Simon Richter
Aidan, > Automake does not seem to differenciate between flex generated c++ files and c > files Not if it has to guess. Use .ll or .l++ as the extension for your lex file, drop the -+ and watch it work. :-) Reason behind that: automake needs to know at Makefile.in generation time which compiler

Flex c++ bug

2003-02-04 Thread Aidan Delaney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Automake does not seem to differenciate between flex generated c++ files and c files Here is the problem balor@navi traditional $ make flex -+ traditional.l++ && mv lex.yy.c traditional.c++ mv: cannot stat `lex.yy.c': No such file or directory make: