[Debichem-devel] Bug#951999: mpqc: FTBFS: messmpi.cc:203:21: error: call to 'MPI_Errhandler_set' declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use MPI_Comm_set_errhandler instead.

[Lucas Nussbaum]

Source: mpqc
Version: 2.3.1-19
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/sh ../../../../libtool --mode=compile mpic++ -DHAVE_CONFIG_H -D_REENTRANT  -I../../../../src/lib -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/src/lib -I/usr/include/mpi -O2  -c messmpi.cc -o messmpi.lo
>  mpic++ -DHAVE_CONFIG_H -D_REENTRANT -I../../../../src/lib -I/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/src/lib -I/usr/include/mpi -O2 -c messmpi.cc  -fPIC -DPIC -o .libs/messmpi.o
> messmpi.cc: In member function 'void sc::MPIMessageGrp::init(MPI_Comm, int*, char***)':
> messmpi.cc:203:21: error: call to 'MPI_Errhandler_set' declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0.  Use MPI_Comm_set_errhandler instead.
>   203 |   MPI_Errhandler_set(commgrp, MPI_ERRORS_ARE_FATAL);
>       |   ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> messmpi.cc: In constructor 'sc::MPIMessageGrp::MPIMessageGrp(const sc::Ref<sc::KeyVal>&)':
> messmpi.cc:132:25: error: call to 'MPI_Errhandler_set' declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0.  Use MPI_Comm_set_errhandler instead.
>   132 |       MPI_Errhandler_set(commgrp, MPI_ERRORS_RETURN);
>       |       ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> make[5]: *** [/<<PKGBUILDDIR>>/src/lib/util/group/../../../../lib/GlobalRules:177: messmpi.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/mpqc_2.3.1-19_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.