On 05/02/2018 16:18, Mattia Rizzolo wrote:
> On Mon, Feb 05, 2018 at 12:48:31PM +, Alastair McKinstry wrote:
>> I think we also need to change powerpc and ppc64 to mpich, as of openmpi3:
> Remember that switching a default mpi requires a library transition, and
> an ordered rebuild of all
On 5 Feb 2018, at 12:48, Alastair McKinstry wrote:
> On 05/02/2018 12:42, James Clarke wrote:
>> Hi,
>> I've just done a team upload of mpi-defaults to add ia64 support, and did a
>> bit
>> of cleanup at the same time (optional->extra, compat and standards version,
Hi,
Deleted the 1.9 tag on salsa.
I think we also need to change powerpc and ppc64 to mpich, as of openmpi3:
"
configure: error: Big endian PPC is no longer supported.
"
regards
Alastair
On 05/02/2018 12:42, James Clarke wrote:
> Hi,
> I've just done a team upload of mpi-defaults to add ia64
On Mon, Mar 16, 2009 at 02:09:06PM +0100, Manuel Prinz wrote:
Also, we should decide (as a project) how to deal with MPI
implementations in general, meaning if we support only one, meaning
that packages build against one we chose, and the others are installed
as libraries, or if we build
A disclaimer: I'm no more a MPI user currently, so take my opinions with
a grain of salt.
On Sat, Mar 14, 2009 at 04:56:41PM +0100, Manuel Prinz wrote:
Am Samstag, den 14.03.2009, 10:54 +0100 schrieb Francesco P. Lovergine:
while working on HDF5 I'm considering to move MPI support to use
Am Montag, den 16.03.2009, 13:43 +0100 schrieb Francesco P. Lovergine:
A disclaimer: I'm no more a MPI user currently, so take my opinions with
a grain of salt.
No worries. My point of view is biased by my Open MPI maintainership.
Any input is welcome if we want to resolve the MPI issues in
Am Samstag, den 14.03.2009, 10:54 +0100 schrieb Francesco P. Lovergine:
while working on HDF5 I'm considering to move MPI support to use
mpi-default-dev
and mpi-default-bin. That would imply providing a single reference platform
support
(openmpi or lam, completely dropping mpich AFAIK)
7 matches
Mail list logo