Hi James On Tue, 20 Aug 2024 at 11:27, James Addison <j...@jp-hosting.net> wrote: > Ok: I can confirm that removing the (OpenMPI-provided) symbols from > the libelpa19.symbols file resolves the build problem, and that > subsequent autopkgtests succeeded on an ARM-based host running when I > ran the binary package build locally within a 32-bit ARM container > environment.
To be clear, which autopkgtests did you run? Those of gpaw? > However: I'm not sure that my suggestion to create per-architecture > symbols is ideal. When trawling through the Debian elpa packaging git > history, I found that the OpenMPI-specific entries were previously > tagged as optional -- and I think that that might be a more convenient > approach. Yes, I think that dates back to a previous time when mpi-defaults were not the same across all architectures. > I've opened a merge request on Salsa with a possible change to do > that: https://salsa.debian.org/debichem-team/elpa/-/merge_requests/1 Merged, thanks. Although I do intend to wait for the mpi-defaults transition to finish before trying to re-introduce the 32-bit binaries. Regards Graham
