Source: hdf5 Version: 1.10.4+repack-10 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link mpicc.openmpi -std=c99 > -pedantic -Wall -Wextra -Wbad-function-cast -Wc++-compat -Wcast-align > -Wcast-qual -Wconversion -Wdeclaration-after-statement > -Wdisabled-optimization -Wfloat-equal -Wformat=2 -Winit-self -Winvalid-pch > -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes > -Wnested-externs -Wold-style-definition -Wpacked -Wpointer-arith > -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum > -Wundef -Wunused-macros -Wunsafe-loop-optimizations -Wwrite-strings > -finline-functions -s -Wno-inline -Wno-aggregate-return > -Wno-missing-format-attribute -Wno-missing-noreturn -O -g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,--version-script,../../../debian/map_mpi.ver > -Wl,-z,relro -o H5make_libsettings H5make_libsettings.o -lsz -lz -ldl -lm > ../../../src/H5Smpio.c:1503:9: error: call to ‘MPI_Type_extent’ declared with > attribute error: MPI_Type_extent was removed in MPI-3.0. Use > MPI_Type_get_extent instead. > 1503 | MPI_Type_extent (old_type, &old_extent); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ../../../src/H5Smpio.c: In function ‘H5S_mpio_hyper_type’: > ../../../src/H5Smpio.c:882:13: error: call to ‘MPI_Type_extent’ declared with > attribute error: MPI_Type_extent was removed in MPI-3.0. Use > MPI_Type_get_extent instead. > 882 | MPI_Type_extent (inner_type, &inner_extent); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > make[4]: *** [Makefile:1603: H5Smpio.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/02/22/hdf5_1.10.4+repack-10_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
