Your message dated Thu, 21 Mar 2019 21:41:22 +0100 with message-id <fe62b13c-1ab4-7659-9114-23d9f6240...@debian.org> and subject line Re: mpqc3: FTBFS: Could NOT find MPI has caused the Debian Bug report #924032, regarding mpqc3: FTBFS: Could NOT find MPI to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mpqc3 Version: 0.0~git20170114-4.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, mpqc3 FTBFS in sid and buster with [...] -- Detecting Fortran/C Interface -- Detecting Fortran/C Interface - Found GLOBAL and MODULE mangling -- Verifying Fortran/CXX Compiler Compatibility -- Verifying Fortran/CXX Compiler Compatibility - Success -- Found PAPI: /usr/lib/x86_64-linux-gnu/libpapi.a -- Found MPI_C: /usr/lib/x86_64-linux-gnu/libmpich.so (found version "3.1") -- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) -- Found MPI_Fortran: /usr/lib/x86_64-linux-gnu/libmpichfort.so (found version "3.1") -- Could NOT find MPI (missing: MPI_CXX_FOUND) (found version "3.1") CMake Error at external/MPI:36 (message): MPI not found Call Stack (most recent call first): external/External:8 (include) CMakeLists.txt:330 (include) -- Configuring incomplete, errors occurred! Andreas BTW, why does it link statically against papi?
mpqc3.buster.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---On Mon, 18 Mar 2019 18:01:51 +0100 Andreas Tille <andr...@an3as.eu> wrote: > > But Alastair mentioned that MPICH was fixed, so yay. > > Please make sure you will care for the bug closing etc. I can confirm that it now builds again ... Andreas
--- End Message ---