Hello Martin,
It is odd that I already had "PMIX_MCA_gds=hash" and still got the
problem on a beowolf with multiple boxes connected by ethernet.
Since the lack of appropriate "#ifdefs" seems like an oversight on the
part of the openmpi developers, I think it would be appropriate to
push it upstre
[moved to ports@]
On Tue, Dec 17, 2019 at 04:16:25PM -0700, Raymond, David wrote:
> Martin,
>
> I have been using openmpi 4.0.2 on my computer system and I found a
> bug that is provoked by running a job (a Go program interfaced to the
> Clang MPI package) on multiple machines connected by ethern
Am 31.10.19 um 15:59 schrieb Martin Reindl:
> Hello,
>
> The attached diff updates devel/openmpi to the current stable release 4.0.2.
> Changelog can be found here:
> https://raw.githubusercontent.com/open-mpi/ompi/v4.0.x/NEWS
> Tested on amd64 and arm64.
>
> Most noteably this update fixes probl
Hello,
The attached diff updates devel/openmpi to the current stable release 4.0.2.
Changelog can be found here:
https://raw.githubusercontent.com/open-mpi/ompi/v4.0.x/NEWS
Tested on amd64 and arm64.
Most noteably this update fixes problems reported by David Raymond off-list.
-m
Index: Makefil
On Fri, Jun 28 2019, Martin Reindl wrote:
> Am 27.06.2019 um 16:09 schrieb Jeremie Courreges-Anglas:
>> Note that what has been committed shouldn't have a problem with NFS: the
>> code in ad_fstype.c already properly checks for f_fstypename and uses
>> it. Our patch is still bogus though, please
Am 27.06.2019 um 16:09 schrieb Jeremie Courreges-Anglas:
Note that what has been committed shouldn't have a problem with NFS: the
code in ad_fstype.c already properly checks for f_fstypename and uses
it. Our patch is still bogus though, please find an additional diff
below. ok?
Yes.
And the
On Tue, Jun 25 2019, Martin Reindl wrote:
> Am 22.06.2019 um 20:09 schrieb Jeremie Courreges-Anglas:
>> On Thu, Jun 06 2019, Martin Reindl wrote:
>>> On Sat, Jun 01, 2019 at 08:03:17PM +0100, Stuart Henderson wrote:
That needs fixing then..
--
Sent from a phone, apologies for poor
Am 22.06.2019 um 20:09 schrieb Jeremie Courreges-Anglas:
On Thu, Jun 06 2019, Martin Reindl wrote:
On Sat, Jun 01, 2019 at 08:03:17PM +0100, Stuart Henderson wrote:
That needs fixing then..
--
Sent from a phone, apologies for poor formatting.
On 1 June 2019 17:15:19 Jeremie Courreges-Anglas
On Thu, Jun 06 2019, Martin Reindl wrote:
> On Sat, Jun 01, 2019 at 08:03:17PM +0100, Stuart Henderson wrote:
>> That needs fixing then..
>> --
>> Sent from a phone, apologies for poor formatting.
>>
>> On 1 June 2019 17:15:19 Jeremie Courreges-Anglas wrote:
>>
>> > On Sat, Jun 01 2019, Stuart He
On Sat, Jun 01, 2019 at 08:03:17PM +0100, Stuart Henderson wrote:
> That needs fixing then..
> --
> Sent from a phone, apologies for poor formatting.
>
> On 1 June 2019 17:15:19 Jeremie Courreges-Anglas wrote:
>
> > On Sat, Jun 01 2019, Stuart Henderson wrote:
> > > Please don't do the huge bump
On Sat, Jun 01, 2019 at 08:03:17PM +0100, Stuart Henderson wrote:
> That needs fixing then..
> --
> Sent from a phone, apologies for poor formatting.
Looks like a candidate for USE_LIBTOOL=gnu, I'll come up with a new diff once
I've done some more testing.
-m
>
> On 1 June 2019 17:15:19 Jeremie
That needs fixing then..
--
Sent from a phone, apologies for poor formatting.
On 1 June 2019 17:15:19 Jeremie Courreges-Anglas wrote:
On Sat, Jun 01 2019, Stuart Henderson wrote:
Please don't do the huge bump for SHARED_LIBS, just a standard major
bump for the existing libraries and start th
On Sat, Jun 01 2019, Stuart Henderson wrote:
> Please don't do the huge bump for SHARED_LIBS, just a standard major
> bump for the existing libraries and start the new ones at 0.0
IIRC the problem is that SHARED_LIBS isn't respected.
> --
> Sent from a phone, apologies for poor formatting.
>
> O
Please don't do the huge bump for SHARED_LIBS, just a standard major bump
for the existing libraries and start the new ones at 0.0
--
Sent from a phone, apologies for poor formatting.
On 31 May 2019 18:55:23 Martin Reindl wrote:
Hello ports@,
here is an update for another port that probabl
Hello ports@,
here is an update for another port that probably get's not much widespread
usage. Nevertheless, this is worthwhile for people running in an MPI-3.1
environment. Tested on macppc, arm64 and amd64. I only needed this once, so
I am not too keen on taking MAINTAINER. Note all fortran bit
15 matches
Mail list logo