Opened 6 years ago

Last modified 4 years ago

#1561 new bug

Wrong autotools selected

Reported by: gropp Owned by:
Priority: minor Milestone: future
Component: mpich Keywords:

Description (last modified by balaji)

The targets created to update the generated files assume that the "right" autotools are first in the path. It would be better to rerun updatefiles (which will use the proper paths). In general, I've found these update rules on other packages to cause problems because they assume certain versions of the autotools. Such rules made sense during the long period when the tools were stable, but not now.

mobile-104-212:mpich2-strict gropp$ make 2>&1 | tee make.log
 cd /Users/gropp/tmp/mpich2/sources/mpich2-trunk && /bin/sh /Users/gropp/tmp/mpich2/sources/mpich2-trunk/confdb/missing --run automake-1.11 --foreign Makefile
aclocal.m4:20: warning: this file was generated for autoconf 2.68.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'. error: Autoconf version 2.63 or higher is required the top level
autom4te: /usr/bin/gm4 failed with exit status: 63
automake-1.11: autoconf failed with exit status: 63
WARNING: `automake-1.11' is probably too old.  You should only need it if
         you modified `', `acinclude.m4' or `'.
         You might want to install the `Automake' and `Perl' packages.
         Grab them from any GNU archive site.
 cd . && /bin/sh ./config.status Makefile depfiles

Change History (3)

comment:1 Changed 6 years ago by goodell

  • Owner set to goodell
  • Status changed from new to accepted

I suspect we can do something about this. I would have expected the "missing" script to respect $AUTOCONF and similar variables, although at first glance this does not appear to be the case.

One possible way to solve this is to patch the "missing" script to respect these variables, and possibly $MPICH2_AUTOTOOLS_DIR as well.

I'll look into this, although at a low-priority level. I still recommend putting the correct versions of all of the autotools together and in your path. If you don't want any automatic rebuild rules then you can pass --disable-maintainer-mode to configure. Switching to a full ./maint/updatefiles run whenever any of these maintainer mode rules is triggered would be both challenging to implement robustly and would cause much unnecessary rebuilding. I really love that only editing a file only causes automake and config.status to be rerun, rather than a full configure run.

comment:2 Changed 6 years ago by balaji

  • Milestone set to future
  • Status changed from accepted to assigned

comment:3 Changed 4 years ago by balaji

  • Description modified (diff)
  • Owner goodell deleted
  • Status changed from assigned to new
Note: See TracTickets for help on using tickets.