This typically happens in one of three cases: 1. You ran autogen.sh (and it didn't complete properly) --> If this is the problem, just rm the source tree, un-tar the tarball again, and just run configure; make install -- don't run autogen.sh.
2. You are building Open MPI on a network filesystem, and the time is not synchronized between the machine on which you are building and the file server --> If this is the problem, make your file server and client machines be synchronized in terms of time 3. You are building Open MPI on a machine with a local time far in the past --> If this is the problem, make your machine have something close to the real time Open MPI's build system is highly dependent upon file timestamps. If the timestamps are inaccurate (e.g., #2 or #3), it gets confused and tries to re-run aclocal (and friends). And just to be clear: it should not be necessary to run autogen.sh (or aclocal or any of its friends) if you are building from an Open MPI distribution tarball. Make sense? Fun fact: as I have typed this email in OS X Mail.app, it keeps trying to autocorrect "aclocal" with "alcohol". Seems somewhat appropriate. ;-) > On Aug 25, 2015, at 7:13 PM, Bryan Flynt <b_fl...@hotmail.com> wrote: > > I'm trying to build OpenMPI_1.8.7 on a RHEL 6.5 system using the default GNU > compilers. The configuration proceeds through and generates the Makefile > but a "make all" immediately errors with a autoconf error (see below). > > I found this exact question already on this list but there was no solution. > The suggestion was to use the pre-packaged tar.gz file but this is already > my starting position so there must be something else to the problem. > > Previous Thread: > http://comments.gmane.org/gmane.comp.clustering.open-mpi.user/21238 > > Any ideas? > Why is "make all" trying to call autoconfig? > > Commands: > > ./configure -prefix=${PWD}/gnu CC=gcc CXX=g++ F77=gfortran FC=gfortran > > make all > > > Error Message (after "make all"): > aclocal.m4:16: warning: this file was generated for autoconf 2.69. > 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'. > configure.ac:40: error: m4_defn: undefined macro: _m4_divert_diversion > configure.ac:40: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2015/08/27492.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
