Re: bison-1.875 patches: yet another success

[Paul Eggert]

"Nelson H. F. Beebe" <address@hidden> writes:

> there is one anomaly that repeats throughout the build log:
> 
>       if ecc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../src -I../lib    -g -MT 
> dirname.o -MD -MP -MF ".deps/dirname.Tpo" \
>         -c -o dirname.o `test -f 'dirname.c' || echo './'`dirname.c; \
>       then mv ".deps/dirname.Tpo" ".deps/dirname.Po"; \
>       else rm -f ".deps/dirname.Tpo"; exit 1; \
>       fi
>       ecc: Command line warning: ignoring option '-M'; no argument required
>       ecc: Command line warning: ignoring option '-M'; no argument required
>       ecc: Command line warning: no action performed for specified object 
> file(s)
>       ecc: Command line warning: ignoring option '-M'; no argument required
>       ecc: Command line warning: ignoring option '-M'; no argument required
>       ecc: Command line warning: no action performed for specified object 
> file(s)
> 
> Evidently, a gcc-specific option (-MT) is being passed to ecc.  That
> didn't happen on other systems where a non-gcc compiler was used.

This sounds like a problem with Automake, not Bison.  To test this
hypothesis I wrote a trivial program to exercise the -M checking
features of configure.  Can you please try it?  To test it, unpack the
attached tar.gz file, and run "configure; make".  I am particularly
interested in the "checking dependency style of gcc..." line.  Thanks.

foo-1.0.tar.gz
Description: trivial program to test dependency checking