Good day Gents, Helmut Grohne, on 2025-05-27: >> how about trying pkgconf and falling back to mpicc? >> >> * When compiling for 64bit case, openmpi will provide mpi-c.pc, so >> that'll be used. >> * When compiling natively on 32bit, mpi-c.pc will be missing and mpicc >> will be used. >> * Cross compiling for 32bit will be broken. >> >> I see two advantages here. One is that we can then generally test cross >> building phyml and will see other possible regressions (on 64bit >> architectures). The other is that I can use phyml as a test case for >> sending patches to mpich.
Andreas Tille, on 2025-05-27: > We are in the process to stop supporting 32bit architectures for any > Debian Med package that might cause trouble. So I guess re-adding > your patch and Build-Depending architecture-is-64-bit could be some > perfectly valid solution. I'm fine with both outcomes. I know I have a slight tendency to fix build failures on 32-bit when issues are somewhat manageable but dropping 32-bit support would be less work for the team as a whole on the long term. If the former option is helpful to Helmut and the general quality of mpich, perhaps it's worth to give 32-bit a chance? Quoting Helmut: >> The patch likely is not appropriate for trixie. How about adding it >> early in forky? I agree to leave the question rest until stabilisation of trixie and implement one of the options at the begining of Debian 14 release cycle. Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/3, please excuse my verbosity `- on air: Subsignal - A Heartbeat Away
signature.asc
Description: PGP signature
