user debian-rele...@lists.debian.org usertag 1075985 + bsp-2025-03-ca-montreal severity 1075985 normal thank you
You're right that the libraries are mis-linked, but in the particular case of fftw MPI, this isn't very serious. Programs using mpi should generally be built with `mpicc`, which will provide the right flags. Some examples of things that work fine: 1. The `mpi-bench` test within fftw3 builds and runs successfully. 2. A set of fftw MPI examples on github builds and runs successfully: https://github.com/nsmith5/FFTW-MPI-Examples/blob/master/example%201/Makefile The (now less severe) bug could be fixed by using something like: MPILIBS="$(shell mpicc --showme:link 2>/dev/null || mpicc -show-link-info)" But this feels a bit too specific to fftw3. I wonder if we could instead have mpi-default-dev provide a pkgconfig file, so that a single command could always provide the right flags.
