I'm actually confused by the changelog on the repo:
- r1 (https://bitbucket.org/devezep/new-romio-for-openmpi) says "Initial import
from branch v1.5"
- r15
(https://bitbucket.org/devezep/new-romio-for-openmpi/changeset/a535d7cdbe79)
then says "Update with openmpi-1.4.3"
...?
Did you not use t
On Fri, 14 Jan 2011, Mohamad Chaarawi wrote:
Hi all,
This seems to break the trunk..
the patch attached seems to fix it..
Thanks -- I applied it to the trunk.
Abhishek
Thanks,
Mohamad
adkul...@osl.iu.edu wrote:
Author: adkulkar
Date: 2011-01-13 15:13:49 EST (Thu, 13 Jan 2011)
New Revi
Hi all,
This seems to break the trunk..
the patch attached seems to fix it..
Thanks,
Mohamad
adkul...@osl.iu.edu wrote:
> Author: adkulkar
> Date: 2011-01-13 15:13:49 EST (Thu, 13 Jan 2011)
> New Revision: 24251
> URL: https://svn.open-mpi.org/trac/ompi/changeset/24251
>
> Log:
> Few fault toler
I just (re?)noticed that your mercurial tree is based on the 1.4 branch:
https://bitbucket.org/devezep/new-romio-for-openmpi
Are we targeting the v1.4 series for this?
I thought we were targeting trunk/v1.5 for the new ROMIO, but perhaps I'm
forgetting something...?
On Jan 14, 2011, a
Jeff Squyres a écrit :
Great!
I see in your other mail that you pulled something from MPICH2 to make this
work.
Does that mean that there's a even-newer version of ROMIO that we should pull in its entirety? It's a little risky to pull most stuff from one released version of ROMIO and then mor
