#1076234 lammps: FTBFS with mpich as default MPI provider on armel, armhf: Fatal error in internal_Comm_set_errhandler: Invalid communicator #1076234
- Package:
- src:lammps
- Source:
- src:lammps
- Submitter:
- Sebastian Ramacher
- Date:
- 2024-07-14 11:33:05 UTC
- Severity:
- normal
- Tags:
Source: lammps Version: 20240207+dfsg-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramacher@debian.org https://buildd.debian.org/status/fetch.php?pkg=lammps&arch=armel&ver=20240207%2Bdfsg-1.1%2Bb4&stamp=1720745050&raw=0 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/debian/tmp/usr/lib/arm-linux-gnueabi \ PYTHONPATH=/<<PKGBUILDDIR>>/debian/python3-lammps/usr/lib/python3.12/dist-packages:${PYTHONPATH} \ python3 demo.py ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. Fatal error in internal_Comm_set_errhandler: Invalid communicator, error stack: internal_Comm_set_errhandler(41812): MPI_Comm_set_errhandler(comm=0xee8f6b74, errh=0xee8f7718) failed internal_Comm_set_errhandler(41770): Invalid communicator [unset]: PMIU_write error; fd=-1 buf=:cmd=abort exitcode=336162565 message=Fatal error in internal_Comm_set_errhandler: Invalid communicator, error stack: internal_Comm_set_errhandler(41812): MPI_Comm_set_errhandler(comm=0xee8f6b74, errh=0xee8f7718) failed internal_Comm_set_errhandler(41770): Invalid communicator : system msg for write_line failure : Bad file descriptor make[1]: *** [debian/rules:131: execute_before_dh_python3-arch] Error 5 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:13: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 Cheers
This looks like a bug in libfakeroot rather than lammps.
Control: reassign -1 src:mpi4py Control: notfixed 1075980 3.1.6-2 Control: fixed 1075980 3.1.6-6 Control: forcemerge 1075980 -1 Control: affcts 1075980 src:lammps The libfakeroot message is a red herring, it's also in precious successful builds. lammps built with the rebuilt lammps, the "Invalid communicator" error message likely indicated that something using openmpi was trying to communicate with something using mpich. cu Adrian
lammps did build with the rebuilt mpi4py cu Adrian