Your message dated Thu, 16 May 2024 10:45:33 +0200 with message-id <ac855123ab340f1111537091f7aec...@debian.org> and subject line mpi4py has caused the Debian Bug report #1069432, regarding mpi4py: FTBFS on armhf: ld: cannot find -llmpe: No such file or directory 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.) -- 1069432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mpi4py Version: 3.1.5-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_build override_dh_auto_build-arch -- \ > --build-args "--mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx" > I: pybuild base:311: /usr/bin/python3.12 setup.py build > --mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx > running build > running build_src > running build_py > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/bench.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/__main__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/run.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/aplus.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/server.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/__main__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/_core.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/_base.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/pool.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/_lib.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/util/dtlib.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/util/pkl5.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/util/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/py.typed -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/bench.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/MPI.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/__init__.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/__main__.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/run.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/dl.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/MPI.pxd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/libmpi.pxd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > copying src/mpi4py/__init__.pxd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.h -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI.h -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.i -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi.pxi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/include/mpi4py > copying src/mpi4py/futures/pool.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/server.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/__init__.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/__main__.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/_lib.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/_core.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/futures/aplus.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/futures > copying src/mpi4py/util/pkl5.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/util/__init__.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > copying src/mpi4py/util/dtlib.pyi -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12/build/mpi4py/util > running build_clib > MPI configuration: [mpi] from 'mpi.cfg' > MPI C compiler: /usr/bin/mpicc > MPI C++ compiler: /usr/bin/mpicxx > checking for library 'lmpe' ... > /usr/bin/mpicc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -c _configtest.c -o _configtest.o > /usr/bin/mpicc -Wl,-z,relro -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 > _configtest.o -llmpe -o _configtest > /usr/bin/ld: cannot find -llmpe: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/04/20/mpi4py_3.1.5-5_unstable-armhf.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message --- mpi4py has continued building successfully and passing tests so I think we can close these bugs.
--- End Message ---
