bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: maintainer-clean and yacc/lex files


From: Allan Saddi
Subject: Re: maintainer-clean and yacc/lex files
Date: Wed, 18 Jul 2001 22:04:09 -0700 (PDT)

Hi again,

It seems to be present in the CVS version as well, although the
problem is a little different. Neither the generated yacc or lex
C files are removed by maintainer-clean. The yacc .h file is
correctly removed if the -d flag is in (AM_)?YFLAGS.

I don't know perl, otherwise I'd submit a patch, but it looks
like lang_yacc_target_hook does not add the generated yacc
C/C++ file to @maintainer_clean_files. Same for lex.

Also, distcheck fails with "Error: files left after distclean".
It seems that the yacc/lex output files are left in the =build
directory.

My test files are available at:
http://philosophysw.com/am-yacclex-test.tar.gz

If you examine the maintainer-clean target in Makefile.in,
you'll see that parser.c and lexer.c are missing. Attempting a
make distcheck also results in a failure.

Thanks.

- Allan

On Wed, 18 Jul 2001, Allan Saddi wrote:

> Sorry about that. I noticed the problem in 1.4 and still saw it
> in 1.4-p5. The diffs are against 1.4-p5. I haven't tried the CVS
> version yet... I'll try it out and let you know if the problem
> still exists.
>
> Thanks for the quick response!
>
> - Allan
>
> On 18 Jul 2001, Tom Tromey wrote:
>
> > >>>>> "Allan" == Allan Saddi <address@hidden> writes:
> >
> > Allan> It seems that maintainer-clean doesn't delete generated yacc/lex
> > Allan> files correctly. If "parser.y" and "lexer.l" are defined in the
> > Allan> source, maintainer-clean attempts to delete "parserc",
> > Allan> "parserh", and "lexerl". It should delete "parser.c",
> > Allan> "parser.h", and "lexer.c" instead.
> >
> > You don't mention what version of automake you are using.
> > This is critical information.
> >
> > This bug has already been fixed in the cvs automake.
> > It might be fixed in one of the later 1.4 releases.  I'm not certain.
> >
> > Tom




reply via email to

[Prev in Thread] Current Thread [Next in Thread]