I need HDF5 for a NETCDF program, and used their recommendation on configuration, which is:
./configure --prefix=/usr/local/hdf5 --with-zlib=/lib64 --enable-hl
There are a number of errors in the config.log. Here are some at the top.
gcc: error: unrecognized command line option ‘-V’
gcc: error: unrecognized command line option ‘-qversion’; did you mean ‘–version’?
conftest.c:11:10: fatal error: ac_nonexistent.h: No such file or directory
conftest.c:57:20: error: expected expression before ‘)’ token
if (sizeof ((off_t)))
^
I’d like to include the entire config.log file, but it says new users can’t upload files.
Since, I can’t attach files (as a new member), here is the output from the configure:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking shell variables initial values... done
checking if basename works... yes
checking if xargs works... yes
checking for cached host... none
checking for config x86_64-unknown-linux-gnu... no
checking for config x86_64-unknown-linux-gnu... no
checking for config unknown-linux-gnu... no
checking for config unknown-linux-gnu... no
checking for config x86_64-linux-gnu... no
checking for config x86_64-linux-gnu... no
checking for config x86_64-unknown... no
checking for config linux-gnu... found
compiler 'gcc' is GNU gcc-7.3.1
expr: syntax error
checking for config ./config/site-specific/host-ip-172-31-33-210.ec2.internal... no
checking for config ./config/site-specific/host-ec2.internal... no
checking for config ./config/site-specific/host-internal... no
checking build mode... production
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
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking if unsupported combinations of configure options are allowed... no
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for off_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking for ptrdiff_t... yes
checking whether byte ordering is bigendian... no
checking size of char... 1
checking size of short... 2
checking size of int... 4
checking size of unsigned... 4
checking size of long... 8
checking size of long long... 8
checking size of __int64... 0
checking size of float... 4
checking size of double... 8
checking size of long double... 16
checking size of __float128... 16
checking size of _Quad... 0
checking quadmath.h usability... yes
checking quadmath.h presence... yes
checking for quadmath.h... yes
checking maximum decimal precision for C... 33
checking if Fortran interface enabled... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in `/home/ec2-user/captain/setup_files/hdf5-1.10.4':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
There should be error or failure messages earlier in the output that may shed more light on the problem. Can you upload the log from “make check”, or else search for “FAILED”, “Error” or “error” and post what you find there?
These are the source files. You can make the changes in the same lines in h5repack_plugin.sh and h5repack.sh (in the build directory) after you’ve configured. If you do it in the .in files, you’ll need to run configure again to get the changes into the scripts run be make check. Conversely, if you make the changes in the .sh files and not in the .sh.in files, configuring again will recreate the .sh files without the changes.
Testing H5Fflush (part1) *** Hint ***
You can use environment variable HDF5_PARAPREFIX to run parallel test files in a
different directory or to add file type prefix. E.g.,
HDF5_PARAPREFIX=pfs:/PFS/user/me
export HDF5_PARAPREFIX
*** End of Hint ***
PASSED
mpiexec has exited due to process rank 0 with PID 0 on
node anirban-desktop exiting improperly. There are three reasons this could occur:
this process did not call “init” before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call “init”. By rule, if one process calls “init”,
then ALL processes must call “init” prior to termination.
this process called “init”, but exited without calling “finalize”.
By rule, all processes that call “init” MUST call “finalize” prior to
exiting or it will be considered an “abnormal termination”
this process called “MPI_Abort” or “orte_abort” and the mca parameter
orte_create_session_dirs is set to false. In this case, the run-time cannot
detect that the abort call was an abnormal termination. Hence, the only
error message you will receive is this one.
This may have caused other processes in the application to be
terminated by signals sent by mpiexec (as reported here).
You can avoid this message by specifying -quiet on the mpiexec command line.
