[MOAB-dev] buildbot failure in Fathom on moab-par

[donotreply at mcs.anl.gov]

The Fathomatic has detected a failed build of moab-par on Fathom.
Full details are available at:
 http://gnep.mcs.anl.gov:8010/builders/moab-par/builds/30

Buildbot URL: http://gnep.mcs.anl.gov:8010/

Buildslave for this Build: gnep

Build Reason: The Nightly scheduler named 'nightly' triggered this build
Build Source Stamp: None
Blamelist: 

BUILD FAILED: failed configure

LOG EXCERPT:
(cached) (cached) checking how to hardcode library paths into programs... immediate
checking for known C compilers... GNU
checking for known compiler/OS combinations... GNU:x86_64
checking for known c++ compilers... GNU
checking for known compiler/OS combinations... GNU:x86_64
checking for gunzip... gunzip -c
checking for gzip... (cached) gunzip -c
checking for zcat... (cached) gunzip -c
checking if C++ compiler supports template class specialization... yes
checking if C++ compiler supports template function specialization... yes
checking how to get verbose linking output from mpif90... -v
checking for Fortran libraries of mpif90...  -L/usr/lib/gcc/x86_64-linux-gnu/4.2.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.2.4/../../.. -lgfortranbegin -lgfortran -lm
checking for dummy main to link with Fortran libraries... none
checking for Fortran name-mangling scheme... lower case, underscore, no extra underscore
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for sys/types.h... (cached) yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for size_t... yes
checking for ptrdiff_t... yes
checking ieeefp.h usability... no
checking ieeefp.h presence... no
checking for ieeefp.h... no
checking for C++ unordered_map... std::tr1
checking mpi.h usability... yes
checking mpi.h presence... yes
checking for mpi.h... yes
checking If mpi.h conflicts with C headers in C++... no
checking for mpiexec... mpiexec
checking for python... python
checking if python works... yes
checking for location of python headers... /usr/include/python2.5
checking pyconfig.h usability... yes
checking pyconfig.h presence... yes
checking for pyconfig.h... yes
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking for NumPy module... yes
checking for location of NumPy includes... /usr/lib/python2.5/site-packages/numpy/core/include
checking for numpy/arrayobject.h... yes
checking if Python support is to be built... no
checking for deflate in -lz... yes
checking for SZ_Decompress in -lsz... no
checking if HDF5 support is enabled... yes
checking for gpfs_stat in -lgpfs... no
configure: error: "~ is not a directory."

sincerely,
 -The Fathomatic