Your message dated Fri, 22 Oct 2021 11:48:40 +0200
with message-id <[email protected]>
and subject line Re: openfoam: FTBFS on m68k: mpi.h: No such file or directory
has caused the Debian Bug report #840462,
regarding openfoam: FTBFS on m68k: mpi.h: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
840462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openfoam
Version: 4.0+dfsg1-3
Severity: important
Justification: fails to build from source
The m68k build of openfoam failed:
PstreamGlobals.H:41:17: fatal error: mpi.h: No such file or directory
#include <mpi.h>
The issue appears to be that debian/rules assumes that mpi-defaults-dev
yields OpenMPI; although that's thankfully valid for all release
architectures nowadays, the non-release architectures m68k and sh4 both
still use MPICH.
Could you please take a look?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--- End Message ---
--- Begin Message ---
Control severity -1 wishlist
At least now, the m68k port is marked "not for us" on the buildds, so I guess
this 5-year old bug should be closed...
--
tobi
On Tue, 11 Oct 2016 14:31:11 -0400 "Aaron M. Ucko" <[email protected]> wrote:
> Source: openfoam
> Version: 4.0+dfsg1-3
> Severity: important
> Justification: fails to build from source
>
> The m68k build of openfoam failed:
>
> PstreamGlobals.H:41:17: fatal error: mpi.h: No such file or directory
> #include <mpi.h>
>
> The issue appears to be that debian/rules assumes that mpi-defaults-dev
> yields OpenMPI; although that's thankfully valid for all release
> architectures nowadays, the non-release architectures m68k and sh4 both
> still use MPICH.
>
> Could you please take a look?
>
> Thanks!
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
>
>
--- End Message ---
