Hi Alastair,
(1) mpi-fort.pc disappeared in recent releases. Is this a regression or is it expected to change? ie will there be more than mpich.pc for pkgconf in the future?
To my knowledge we have never shipped this file. There has been an open issue asking for these (https://urldefense.us/v3/__https://github.com/pmodels/mpich/issues/6845__;!… ). It seems to have fallen thru the cracks. Perhaps we can get this in the 5.0.0beta due out in November.
(2) I would like to enable a build for both GPUs and non-GPU systems. Currently a GPU-enabled build will fail to run on a non-GPU machine unless an environment variable is set to override this.
This is now resolved in the main branch and will be included in the 5.0.0beta. If desired, we can look at backporting to the 4.3.x branch for a bug-fix release.
Ken
From: Alastair McKinstry via devel <devel(a)mpich.org>
Date: Monday, September 15, 2025 at 4:08 AM
To: devel(a)mpich.org <devel(a)mpich.org>
Cc: Alastair McKinstry <mckinstry(a)debian.org>
Subject: [mpich-devel] MPICH in Debian/Linux
This Message Is From an External Sender
This message came from outside your organization.
Hi
I maintain mpich within Debian Linux (currently at version 4.3.1).
I have two questions I am trying to find answers for:
(1) mpi-fort.pc disappeared in recent releases. Is this a regression or
is it expected to change? ie will there be more than mpich.pc for
pkgconf in the future?
(2) I would like to enable a build for both GPUs and non-GPU systems.
Currently a GPU-enabled build will fail to run on a non-GPU machine
unless an environment variable is set to override this.
This is cumbersome for most uses. It would be preferable to have a
default /etc config file setting behaviour.
Is this possible?
Best regards
Alastair
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: mckinstry(a)debian.org, im: @alastair:mckinstry.ie
https://urldefense.us/v3/__https://mastodon.ie/@amckinstry__;!!G_uCfscf7eWS…
