Autoconf warnings should probably be enabled by default

R. Diez rdiezmail-rtems at yahoo.de
Thu Jul 25 09:02:21 UTC 2013


Hi all:

I just enabled on my PC autoconf's warnings (in script 'bootstrap', I added "--warnings=all" to the 'autoreconf' invocation), and sure enough I got quite a lot of them.

Is this not an area worth cleaning up? I am generally not a friend of disabling (or not enabling) warnings.

There seems to be 2 types of warnings that come up all the time:

1) sp01/Makefile.am:18: warning: user target 'sp01$(EXEEXT)' defined here ...
/home/blah...blah/automake-1.13/am/program.am: ... overrides Automake target 'sp01$(EXEEXT)' defined here

In that particular case, that's the rule in question:

sp01$(EXEEXT): $(sp01_OBJECTS) $(sp01_DEPENDENCIES)
    @rm -f sp01$(EXEEXT)
    $(make-exe)

I am no autoconf expert, but I guess the configuration is requesting standard program compilation and then defining its own rule about how to build a program.

2) File doc/project.am is redefining TEXI2DVI and the like, which autoconf does not like either.

If those redefinitions make sense (I cannot tell myself), I guess the files could use variables with different names.

Thanks,
  rdiez




More information about the devel mailing list