Re: JAVAROOT was already defined

[Simon Josefsson]

Simon Josefsson <address@hidden> writes:

> The Makefile.am below generate the following errors during autoreconf:
>
> ...
> configure.ac: installing `./install-sh'
> configure.ac: installing `./missing'
> Makefile.am: installing `./INSTALL'
> doc/Makefile.am:28: installing `doc/mdate-sh'
> doc/Makefile.am:28: installing `doc/texinfo.tex'
> examples/Makefile.am: installing `./depcomp'
> /usr/share/automake-1.8/am/java.am: JAVAROOT was already defined in condition 
> ENABLE_JAVA, which is included in condition TRUE ...
> java/Makefile.am:35:   while processing `libidn_jar_JAVA'
> java/Makefile.am:29: ... `JAVAROOT' previously defined here
> /usr/share/automake-1.8/am/java.am: JAVAROOT was already defined in condition 
> ENABLE_JAVA, which is included in condition TRUE ...
> java/Makefile.am:35:   while processing `libidn_jar_JAVA'
> java/Makefile.am:29: ... `JAVAROOT' previously defined here
> autoreconf: Leaving directory `.'
> $ 
>
> I don't understand the warning.  JAVAROOT appears to be documented as
> a user variable.  Am I not allowed to modify it?  From the manual:
>
> `JAVAROOT'
>      The value of this variable is passed to the `-d' option to
>      `javac'.  It defaults to `$(top_builddir)'.
>
...
> 2004-03-19  Alexandre Duret-Lutz  <address@hidden>
>
>       Overriding JAVAROOT is legitimate, do not warn about it.
>       * lib/Automake/Variable.pm (%_silent_variable_override): Add JAVAROOT.
>       * tests/java2.test: Run automake without -Wno-override.
>       Report from Simon Josefsson.

Alas, I still have this problem.  I need to comment out JAVAROOT from
every /usr/share/automake-*/am/java.am file I get from Debian, to
avoid the re-definition error.  Debian is now up to version 1.9.4, and
I can verify that the patch is part of their copy.

(Running 'autoreconf -fvi' inside
http://josefsson.org/libidn/releases/libidn-0.5.12.tar.gz should
trigger this.)

Thanks.