xmpi fails to configure with compilers that are more restrictive about
parameters to main, because the configure test uses
#include <lam.h>
int
main(int argc, char* argv)
{ return 0; }
which has char *argv instead of char *argv[]. This is likely not intended,
because config/mpi_check_trillium.m4 says
cat > conftest.$ac_ext <<EOF
#include <lam.h>
int
main(int argc, char* argv[])
{ return 0; }
EOF
but the [] is understood as quoting character in m4.
Best,
Michael
tags 702438 patch thanks The attached patch fixes quoting in config/mpi_check_trillium.m4 and config/lsc_find_motif.m4.
We believe that the bug you reported is fixed in the latest version of
xmpi, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 702438@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Graham Inggs <graham@nerve.org.za> (supplier of updated xmpi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 23 Jul 2014 23:55:56 +0200
Source: xmpi
Binary: xmpi libxmpi4 libxmpi4-dev
Architecture: source amd64
Version: 2.2.3b8-13.2
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire <camm@debian.org>
Changed-By: Graham Inggs <graham@nerve.org.za>
Description:
libxmpi4 - Graphical user interface for MPI program development
libxmpi4-dev - Graphical user interface for MPI program development
xmpi - Graphical user interface for MPI program development
Closes: 544775 702438 728008 750928
Changes:
xmpi (2.2.3b8-13.2) unstable; urgency=medium
.
[ Adam Conrad ]
* Replace home-grown config.{sub,guess} magic with dh_autotools-dev.
.
[ Daniel T Chen ]
* Use dh-autoreconf for newer arches (Closes: #728008, #544775).
* Fix build with (non-)extant directories.
.
[ Graham Inggs ]
* Non-maintainer upload.
* Fix quoting in M4 macros (Closes: #702438).
* Remove diffs to generated files from d/patches/3.0-quilt-source-init.
* Remove leftover d/xmpi1-runtime directory.
* Build with hardening and --as-needed flags (Closes: #750928).
Checksums-Sha1:
ff3e58a0190faf6510865c5e9a4257cca0b9122a 1816 xmpi_2.2.3b8-13.2.dsc
97881c66ffc083a1892c69c5cc780cb3914f61ce 9712 xmpi_2.2.3b8-13.2.debian.tar.xz
b2ace3291749e7e31ccd7a7780229455d0e72d93 94104 xmpi_2.2.3b8-13.2_amd64.deb
c9406c4b211a7b187e36311642d28432be7522e0 32592 libxmpi4_2.2.3b8-13.2_amd64.deb
0dd498da300294cd5bbe92b27dec1190f6dfb888 46996 libxmpi4-dev_2.2.3b8-13.2_amd64.deb
Checksums-Sha256:
3727475add088251e71e84d3d334e4657ec7233658b61c0dd95f56854d879b80 1816 xmpi_2.2.3b8-13.2.dsc
05b6017aa7a4be492b159d5fd6f28fd46001ecc9b8c2b12776ea8498e7da3240 9712 xmpi_2.2.3b8-13.2.debian.tar.xz
8f18a707e6c7b5647ed78a01bc10ab07c22598ad459d3955af891bf48070c055 94104 xmpi_2.2.3b8-13.2_amd64.deb
52f19e7aa7604fe254d1826b76322c7c86476c624f8c30377dcac69c5c20b829 32592 libxmpi4_2.2.3b8-13.2_amd64.deb
64c1829dbb0244d8312d52dcb922f73d577c966b238e21e3b5f11fcb0a9985cc 46996 libxmpi4-dev_2.2.3b8-13.2_amd64.deb
Files:
faaf93a6f0bfc856e976bdb10bd0f0dd 94104 devel extra xmpi_2.2.3b8-13.2_amd64.deb
b29fe69ed58c5f0794bf27eacc87a34f 32592 libs extra libxmpi4_2.2.3b8-13.2_amd64.deb
70df8c55f7db9e5e119f2946a93ff1d2 46996 libdevel extra libxmpi4-dev_2.2.3b8-13.2_amd64.deb
fb3513516c4e9010b0f52237424bba8e 1816 devel extra xmpi_2.2.3b8-13.2.dsc
4e121be8bffb15ff51a52bf8fc9cfc67 9712 devel extra xmpi_2.2.3b8-13.2.debian.tar.xz
iQIcBAEBCgAGBQJT0DH4AAoJEACQ/CG1zRrMqMkQAKpy4BKfJ3TFwJzlwTnYJtiO
cRspiqgzRVZQH03g5lTx1S6hD7NoQwjyjT12dVZda+Av+OhcPr0QSFMMVDgjgjk9
BV756PUNAsJKJg1T/CWpSqi4xaRkCxjHMeDHWix1MMLftcEOMljQ2iaNlfAxuZMI
VFfkGt8d6S+hbtgpK5tWG8VTHP9byS4Kh1nXHUCey7qBMssQwsk7G/LJcN44BS6W
i5RW0bH/bW8sAb+dGXEC50KfbVOukhLE4FoiHqby/NXZt/b1szfROyb/3wzIagQw
3v7pV72vdmRUU/ieE6kAFVUUQzoDQwa54MQcIVQMarkfrdjLk89W+f/1gsKmho1k
QVon3SC9Ywhn/mvVUH7YXOYZsFWMMxFzkUvhPkMGEaXBOvU/Aibj7vggwpK40iBb
MM7eqHfNxh83+QrG296j3XmHxs80W8xC8SGQtkOPG9Xu169qATYlDQsxyslFAtdn
UDg8nxdB1hmaOM4uqF5Y+LAnUkvbrQg0MO9mj/sbYfSLNoQHRZ9iwJjal375qe7/
B4Co71E3CaoEQpksyc5CP3aeuqvJV7H5dwBeqKlF6CXfaxJV8WrIKYfXwDAqb6wR
jcUnTDZesrXIpPCiXy4dPyuAXzMHqP/ZauEmpGi0Ndo0VjTkOv1/CccwYzEluEWt
ouK9HeMnxU059OlBKdEW
=k58i
-----END PGP SIGNATURE-----
Thanks a lot for fixing the problem reported earlier, but I'm afraid there's one more such case of missing quotes: config/mpi_check_mpi_h.m4 should be fixed in the same way as the other two .m4 files. Thanks a lot, Michael
Hi Michael I've fixed the one you mentioned as well as another two; config/cxx_find_template_repository.m4 and config/cxx_have_broken_getline.m4. Please try building again with the attached updated patch. Regards Graham
Hi Graham, Apologies for taking so long to get back to this. I can now confirm that the package builds fine with the complete set of patches that you proposed. Best, Michael
Hi Camm. as I said previously I consider you perfectly active. Since you did not answered my mail below I assume you might be to busy. I hope you are welcoming the NMU I did intentionally to the largest delay period possible of 15 days. You can find all changes in Git at https://salsa.debian.org/debian/xmpi Please let me know if I should cancel this NMU. Kind regards Andreas. Am Wed, Mar 11, 2026 at 08:09:07AM +0100 schrieb Andreas Tille:
Greetings, and thank you so much for your kind and thoughtful message, and your concern for improving Debian! I love git, and use it to maintain GCL and AXIOM upstream at the moment. While in principle it might be a good idea to think of maintaining the packaging files that way as well, for the moment it is a bit too much complexity for my taste. I would eventually be approving everything from email notifications anyway, and would not like to frustrate would be contributors with an expectation of high commit volume. So for now I am happy with the source packages from the Debian archive. As for xmpi, like lam, upstream development has ceased, but these tools are still useful in diagnosing and visualizing mpi traffic and systems, as well as supporting legacy software using it, all with minimal maintenance requirements. Seems no reason to abandon them. Much of the value of Debian is in keeping archival software alive and accessible whenever the interest arises. Take care, Andreas Tille <andreas@an3as.eu> writes:
We believe that the bug you reported is fixed in the latest version of
xmpi, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 702438@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <tille@debian.org> (supplier of updated xmpi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 04 Apr 2026 23:30:04 +0200
Source: xmpi
Architecture: source
Version: 2.2.3b8-14.1
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire <camm@debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Closes: 702438
Changes:
xmpi (2.2.3b8-14.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Andreas Tille ]
* Maintain in Debian team on Salsa
* Add Homepage
* d/watch:
- Version: 5
- Mark Untrackable
* d/copyright: DEP5
* d/README.Debian: Removed since only purpose was to point to webpage that
does not exist any more
* debhelper-compat (= 13)
* Standards-Version: 4.7.4 (Remove Priority field)
.
[ Graham Inngs ]
* Really fix quoting in M4 macros
Closes: #702438
Checksums-Sha1:
145aee007b001600ec5d2a22b11a4ec777871401 1956 xmpi_2.2.3b8-14.1.dsc
247b697eac33d07d77622b6698b4e21bf0c5c92a 9916 xmpi_2.2.3b8-14.1.debian.tar.xz
0f595292a7f9a9e982bf5a90e6ab41e934cb2ebb 8951 xmpi_2.2.3b8-14.1_amd64.buildinfo
Checksums-Sha256:
3c9d62681e3d4c83e269255ac9a22d95fb712e1f33f114b21b51c40edac60aed 1956 xmpi_2.2.3b8-14.1.dsc
d6f76db2789ac4a9a22fccb516f6f1a51f0738aba2ed6d3f2a82fc21b01fcce8 9916 xmpi_2.2.3b8-14.1.debian.tar.xz
b639d6a1edaf2272dfc5ff7aec0e4291e11d5be00e58ca28e2b5932d736643ce 8951 xmpi_2.2.3b8-14.1_amd64.buildinfo
Files:
42661cebeccb8386ef047beddfdd479c 1956 devel optional xmpi_2.2.3b8-14.1.dsc
abcafb97f894a9497b1a939cc00d73a0 9916 devel optional xmpi_2.2.3b8-14.1.debian.tar.xz
acb83c6c7572b3c5263f088aba0aeb59 8951 devel optional xmpi_2.2.3b8-14.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmnRg5cRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEHcA/9FN0iBRbngB64D38j91iiWx/vS/lXXMMf
sy39CDA1M+T3z7BQc4ZzzbHgk+LB1YyGYjt2IFNY7tfzpgV0t6IcfnF2cTyy6yqU
jUtdHYF6aog9hyiOvHeMo1ZXLgfN1pRLOy2Dx9WppG50Xn4i0p4RA9sFhENspcmP
z/tDYEWIP+7KVsK7BLg8paRTDWC81196hv5kvD8qOQCyvZsN7WbZsqe+OhW1ojfi
8J9jt8HbexPRhkHJbUz6p1HHtsWd/8zQclcO5P7RwTvJ6NmX2FY0ssDZBZHZU8Oq
xEr6cDEKSXtgsaxtvbGVbz6gRuloW1ZzYCTVl8W7maf0Ze7TQbkCRClVCYSr8+Fr
TmjCKmI5CR6BC/3DgwspUDw15dORzT09Q4KGM9SoFZ3RJpcAqm0TERURKgP854cy
viNNIrd8f4ibCDgeEr5cAOr31b0Tsxvub5JpKyaZmW7SOWi0i7rSq8pqsrnQg+bz
BOPANMhN0cg1x8o6L8VWDPfXzA/gY7Thhs5biQBZ4GCTmTAg/ToaI7Kh0+M+TSFG
rcqp7FWOwieuNLQRmeBZc/gGakJVuVeBvYFpIDxzYIVeaiz6amjpt0ILspSGKlG3
2rU8TBjjnrlGHr29khTVyNwHKjcoTKMFinuraXgNvSH4Y9vJ8wgvwASWl5FjKEJw
uEFQH32zOw4=
=ZcUK
-----END PGP SIGNATURE-----
Hi again, I noticed your later upload incorporating the changes from the NMU. I realize now that I probably misunderstood the intention of your previous mail. Had you explicitly asked me to cancel the NMU from DELAYED I would of course have done so. I also appreciated your remarks about the value of keeping archival and legacy software available in Debian. I fully agree with this perspective, and packages like xmpi and lam are exactly the kind of software where long-term availability in Debian matters. Thanks as well for clarifying your perspective on Git-based packaging workflows. My own experience has been quite positive, especially regarding collaboration and reducing maintenance overhead for occasional contributors, so I tend to look at this differently. Regarding future maintenance: would you prefer to keep the existing Salsa repository available as an optional collaboration point, or would you rather have it removed? Kind regards Andreas. Am Wed, Apr 08, 2026 at 08:10:12PM -0400 schrieb Camm Maguire: