[Debichem-devel] Bug#1076025: RM: elpa [armel armhf i386] -- ROM; FTBFS on 32-bit architectures

[Graham Inggs]

Hi James

On Mon, 19 Aug 2024 at 12:06, James Addison <jay at jp-hosting.net> wrote:
> I've been taking a quick look at this while inspecting the status of
> the python3.12-only transition (as gpaw is one of the few remaining
> blockers there, and depends on elpa).
>
> From the build logs: the failure seems to be due to the missing
> mpi_fortran_... symbols on 32-bit ARM; but those appear to be openmpi
> symbols -- if the default MPI provider is (or should now be) mpich,
> then should those symbols be removed from the debian/libelpa19.symbols
> file?
>
> ...and, conversely: why are 64-bit builds successfully linking openmpi
> and resolving those symbols, if mpich is meant to be the default?
>
> (it's likely that I don't understand the context, but I wanted to ask
> to make sure that we're not unnecessarily dropping some supported
> architectures from elpa)

The default MPI was only changed to mpich on 32-bit architectures, on
64-bit architectures, it remains openmpi.

See #1064810:
"OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH."

Regards
Graham