It looks like you are having timestamp issues, e.g.:
make: Warning: File `Makefile.am' has modification time 3.6e+04 s in
the future
We typically see this in environments where NFS clients are not time
synchronized properly with the NFS server (e.g., using ntp either to
the NFS server directly, or to a common parent ntp server, or something
similar).
Automake-derived build systems are *extremely* sensitive to filesystem
timestamps because they are driven off Makefile dependencies. So if
you are working on a networked filesystem and do not have your time
tightly synchronized between the client and server, these kinds of
errors will occur.
Two fixes for this are:
1. Fix the time issues between network filesystem client and server
2. Build on a non-networked filesystem
On Aug 8, 2005, at 6:19 AM, Sridhar Chirravuri wrote:
Hi,
I was trying to build the latest code but as I mentioned in one of my
previous mails, build is getting into a loop.
[root@micrompi-1 ompi]# make all | tee mymake.log
make: Warning: File `Makefile.am' has modification time 3.6e+04 s in
the future
cd . && /bin/sh /ompi/config/missing --run aclocal-1.9
/usr/share/aclocal/libgcrypt.m4:23: warning: underquoted definition of
AM_PATH_LIBGCRYPT
run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/ao.m4:9: warning: underquoted definition of
XIPH_PATH_AO
cd . && /bin/sh /ompi/config/missing --run automake-1.9 --foreign
cd . && /bin/sh /ompi/config/missing --run autoconf
/bin/sh ./config.status --recheck
/bin/sh ./config.status
Making all in config
make[1]: make[1]: Entering directory `/ompi/config'
Warning: File `Makefile.am' has modification time 3.6e+04 s in the
future
cd .. && make am--refresh
make[2]: Entering directory `/ompi'
make[2]: Warning: File `Makefile.am' has modification time 3.6e+04 s
in the future
cd . && /bin/sh /ompi/config/missing --run aclocal-1.9
/usr/share/aclocal/libgcrypt.m4:23: warning: underquoted definition of
AM_PATH_LIBGCRYPT
run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/ao.m4:9: warning: underquoted definition of
XIPH_PATH_AO
cd . && /bin/sh /ompi/config/missing --run automake-1.9 --foreign
cd . && /bin/sh /ompi/config/missing --run autoconf
/bin/sh ./config.status --recheck
/bin/sh ./config.status
make[2]: warning: Clock skew detected. Your build may be incomplete.
make[2]: Leaving directory `/ompi'
make[2]: Entering directory `/ompi'
make[2]: Warning: File `Makefile.am' has modification time 3.6e+04 s
in the future
cd . && /bin/sh /ompi/config/missing --run aclocal-1.9
/usr/share/aclocal/libgcrypt.m4:23: warning: underquoted definition of
AM_PATH_LIBGCRYPT
run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/ao.m4:9: warning: underquoted definition of
XIPH_PATH_AO
cd . && /bin/sh /ompi/config/missing --run automake-1.9 --foreign
cd . && /bin/sh /ompi/config/missing --run autoconf
/bin/sh ./config.status --recheck
/bin/sh ./config.status
make[2]: warning: Clock skew detected. Your build may be incomplete.
make[2]: Leaving directory `/ompi'
cd .. && make am--refresh
make[2]: make[2]: Entering directory `/ompi'
Warning: File `Makefile.am' has modification time 3.6e+04 s in the
future
cd . && /bin/sh /ompi/config/missing --run aclocal-1.9
/usr/share/aclocal/libgcrypt.m4:23: warning: underquoted definition of
AM_PATH_LIBGCRYPT
run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/ao.m4:9: warning: underquoted definition of
XIPH_PATH_AO
cd . && /bin/sh /ompi/config/missing --run automake-1.9 --foreign
make[2]: *** [Makefile.in] Interrupt
make[1]: *** [../configure] Interrupt
make: *** [all-recursive] Interrupt
The config.status –recheck is being issued from Makefile. I have moved
config.status to config.status.old and did touch config.status but
still “make all” is going in loop.
Is anyone tried building the latest code drop of OpenMPI? Or Is anyone
has seen this type of behavior?
Please let me know.
Thanks
-Sridhar
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
