Ok, weird.  Try running the process again (untar, configure, make) but use 
"make -d" and capture the entire output so that you can see what file(s) 
is(are) triggering Automake to invoke aclocal during the build (it will be a 
*LOT* of output).


> On Sep 1, 2016, at 1:20 PM, Sean Ahern <s...@ensight.com> wrote:
> 
> Yep, that's it.
> -Sean
> 
> --
> Sean Ahern
> Computational Engineering International
> 919-363-0883
> 
> 
> On Thu, Sep 1, 2016 at 1:04 PM, Jeff Squyres (jsquyres)
> <jsquy...@cisco.com> wrote:
>> That's odd -- I've never seen this kind of problem happen on a 
>> locally-mounted filesystem.
>> 
>> Just to make sure: you're *not* running autogen.pl, right?  You're just 
>> basically doing this:
>> 
>> -----
>> $ tar xf openmpi-2.0.0.tar.bz2
>> $ cd openmpi-2.0.0
>> $ ./configure ...
>> $ make ...
>> -----
>> 
>> Right?
>> 
>> 
>>> On Sep 1, 2016, at 12:51 PM, Sean Ahern <s...@ensight.com> wrote:
>>> 
>>> Greetings, Jeff.
>>> 
>>> Sure, I could see that. But I'm trying to run on a locally mounted 
>>> filesystem in this case. I may need to run make in debug mode and see what 
>>> it thinks is out of date. See if you guys can help me track down the 
>>> dependency problem.
>>> 
>>> -Sean
>>> 
>>> --
>>> Sean Ahern
>>> Computational Engineering International
>>> 919-363-0883
>>> 
>>> On Thu, Sep 1, 2016 at 11:56 AM, Jeff Squyres (jsquyres) 
>>> <jsquy...@cisco.com> wrote:
>>> Greetings Sean.
>>> 
>>> Yes, you are correct - when you build from the tarball, you should not need 
>>> the GNU autotools.
>>> 
>>> When tarball builds fail like this, it *usually* means that you are 
>>> building in a network filesystem, and the time is not well synchronized 
>>> between the machine on which you are building and the network filesystem 
>>> server.  Specifically: GNU Autotools-based builds are heavily dependent 
>>> upon filesystem timestamps.  If the sync is off between a network 
>>> filesystem client and server, all kinds of things go wrong (to include 
>>> thinking that it needs to run the autotools as part of the build).
>>> 
>>> 
>>> 
>>>> On Sep 1, 2016, at 11:47 AM, Sean Ahern <s...@ensight.com> wrote:
>>>> 
>>>> I'm trying to compile OpenMPI 2.0.0 on a CentOS 6.7 system and am running 
>>>> into what appears to be a very basic problem. I'm hoping someone here can 
>>>> give me a pointer. (I'll have more involved questions later.) I've looked 
>>>> through the FAQ for an answer and didn't see anything related. And I don't 
>>>> see any messages in the archives from the last several years about this.
>>>> 
>>>> I'm using the tarball 2.0.0 release, which presumably shouldn't require 
>>>> the GNU autotools. But, after running "configure", the subsequent "make" 
>>>> fails, trying to run aclocal-1.15.
>>>> 
>>>> Here's running configure:
>>>> 
>>>> % ./configure --prefix=blah/blah/openmpi-2.0.0 --disable-java 
>>>> --disable-mpi-fortran
>>>> ============================================================================
>>>> == Configuring Open MPI
>>>> ============================================================================
>>>> 
>>>> *** Startup tests
>>>> checking build system type... x86_64-unknown-linux-gnu
>>>> checking host system type... x86_64-unknown-linux-gnu
>>>> checking target system type... x86_64-unknown-linux-gnu
>>>> checking for gcc... gcc
>>>> checking whether the C compiler works... yes
>>>> checking for C compiler default output file name... a.out
>>>> checking for suffix of executables...
>>>> checking whether we are cross compiling... no
>>>> … lots of output …
>>>> config.status: creating ompi/mpiext/cuda/c/mpiext_cuda_c.h
>>>> config.status: ompi/mpiext/cuda/c/mpiext_cuda_c.h is unchanged
>>>> config.status: executing depfiles commands
>>>> config.status: executing 
>>>> opal/mca/event/libevent2022/libevent/include/event2/event-config.h commands
>>>> config.status: executing libtool commands
>>>> 
>>>> Seems fine. (If someone wants the full "configure" output, I'll send it.)
>>>> But when I run "make", I immediately get this:
>>>> 
>>>> % make all
>>>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh 
>>>> /home/sean/work/thirdparty/trunk/OpenMPI/openmpi-2.0.0/config/missing 
>>>> aclocal-1.15 -I config
>>>> /home/sean/work/thirdparty/trunk/OpenMPI/openmpi-2.0.0/config/missing: 
>>>> line 81: aclocal-1.15: command not found
>>>> WARNING: 'aclocal-1.15' is missing on your system.
>>>>         You should only need it if you modified 'acinclude.m4' or
>>>>         'configure.ac' or m4 files included by 'configure.ac'.
>>>>         The 'aclocal' program is part of the GNU Automake package:
>>>>         <http://www.gnu.org/software/automake>
>>>>         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
>>>>         <http://www.gnu.org/software/autoconf>
>>>>         <http://www.gnu.org/software/m4/>
>>>>         <http://www.perl.org/>
>>>> make: *** [aclocal.m4] Error 127
>>>> 
>>>> I haven't modified any m4 files. Indeed, I haven't modified anything. I 
>>>> simply ran "configure" and then "make". What am I doing wrong? I feel like 
>>>> there's something very basic failing here.
>>>> 
>>>> (I have attached my bzip2ed config.log file here.)
>>>> 
>>>> -Sean
>>>> 
>>>> --
>>>> Sean Ahern
>>>> Computational Engineering International
>>>> 919-363-0883
>>>> <config.log.bz2>_______________________________________________
>>>> users mailing list
>>>> users@lists.open-mpi.org
>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>>> 
>>> 
>>> --
>>> Jeff Squyres
>>> jsquy...@cisco.com
>>> For corporate legal information go to: 
>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>> 
>>> _______________________________________________
>>> users mailing list
>>> users@lists.open-mpi.org
>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>>> 
>>> _______________________________________________
>>> users mailing list
>>> users@lists.open-mpi.org
>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
>> 
>> 
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to: 
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>> 
>> _______________________________________________
>> users mailing list
>> users@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

_______________________________________________
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users

Reply via email to