Re: [bug-GNUnet] configure doesn't check automake version

[Christian Grothoff]

On Saturday 04 December 2004 13:28, Octávio Filipe Gonçalves wrote:
> Hi,
>
> While I do ./configure for the latest version of GnuNet there's nothing
> saying I need aclocal or automake or perl, but when I do 'make' I get
> the following errors:
>
> address@hidden GNUnet]$ make
> cd . && /bin/sh /home/gnunet/GNUnet/missing --run aclocal-1.8 -I m4
> /home/gnunet/GNUnet/missing: line 52: aclocal-1.8: command not found
> WARNING: `aclocal-1.8' is missing on your system.  You should only need
> it if
>          you modified `acinclude.m4' or `configure.ac'.  You might want
>          to install the `Automake' and `Perl' packages.  Grab them from
>          any GNU archive site.
>  cd . && /bin/sh /home/gnunet/GNUnet/missing --run automake-1.8 --gnu
> /home/gnunet/GNUnet/missing: line 52: automake-1.8: command not found
> WARNING: `automake-1.8' is missing on your system.  You should only need
> it if
>          you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
>          You might want to install the `Automake' and `Perl' packages.
>          Grab them from any GNU archive site.
> cd . && /bin/sh /home/gnunet/GNUnet/missing --run autoconf
> autoconf: configure.in: No such file or directory
> make: *** [configure] Error 1
>
> I didn't change anything on any configuration files, Makefile.am ,
> acinclude.m4 or configure.ac.
>
> The problem is that
>
> address@hidden GNUnet]# automake --version
> automake (GNU automake) 1.4-p6
>
> and GNUnet requires  automake (>= 1.7.6)
> <http://www.gnu.org/software/automake/>
> so... shouldn't configure check if the automake installed is a version
> prior to 1.7.6?

No, it should not check for automake since it does not depend on 
automake/autoconf/perl/m4 in any particular version _unless_ 
configure.ac/Makefile.am/Makefile.in were somehow changed.  Now, if you're 
absolutely positive that you did not touch these files (I would re-extract 
the tar ball and try again to be sure), and it does what you show above, then 
this would be a bug in autoconf/automake on your system (and not GNUnet), and 
I would try to report it to the automake/autoconf community.  But I seriously 
doubt that this is the case, maybe you touched one of these files by accident 
and forgot about it?  

Christian