On Sep 14, 2013, at 12:21 PM, Huangwei wrote:
> do i=1, N-1
> allocate (QRECS(A(i)))
> itag = i
> call mpi_recv(QRECS..., i, itag, .)
> deallocate(QRECS)
> enddo
I assume you're doing more than just allocate/mpi_recv/deallocate
Thanks very much, have a nice weekend!
best regards,
Huangwei
On 15 September 2013 11:29, Jeff Squyres (jsquyres) wrote:
> On Sep 14, 2013, at 12:21 PM, Huangwei wrote:
>
> > do i=1, N-1
> > allocate (QRECS(A(i)))
> > itag = i
> > call mpi_recv(QRECS..
I'm not entirely sure - I don't see anything that would cause that problem in
that location. How did you configure this?
On Sep 12, 2013, at 3:17 AM, Matthieu Brucher
wrote:
> Hi,
>
> I compiled OpenMPI on a RHEL6 box with LSF support, but when I run
> sonthing, it crashes. Also orte-info cr
Just --with-lsf. Perhaps because then it must be launched through lsf?
Le 15 sept. 2013 18:02, "Ralph Castain" a écrit :
> I'm not entirely sure - I don't see anything that would cause that problem
> in that location. How did you configure this?
>
>
> On Sep 12, 2013, at 3:17 AM, Matthieu Brucher
No - out of curiosity, does ompi_info work? I'm wondering if this is strictly
an orte-info problem.
On Sep 15, 2013, at 10:03 AM, Matthieu Brucher
wrote:
> Just --with-lsf. Perhaps because then it must be launched through lsf?
>
> Le 15 sept. 2013 18:02, "Ralph Castain" a écrit :
> I'm not e
Yes, ompi_info does not crash.
Le 15 sept. 2013 18:05, "Ralph Castain" a écrit :
> No - out of curiosity, does ompi_info work? I'm wondering if this is
> strictly an orte-info problem.
>
> On Sep 15, 2013, at 10:03 AM, Matthieu Brucher
> wrote:
>
> Just --with-lsf. Perhaps because then it must b
Could you try the current 1.7.3 nightly tarball instead? I don't see a problem
there, and I'm wondering if this is something we already fixed. We will be
releasing 1.7.3 shortly and it is mostly complete at this time.
On Sep 15, 2013, at 10:43 AM, Matthieu Brucher
wrote:
> Yes, ompi_info doe
I can try later this week, yes.
Thanks
Le 15 sept. 2013 19:09, "Ralph Castain" a écrit :
> Could you try the current 1.7.3 nightly tarball instead? I don't see a
> problem there, and I'm wondering if this is something we already fixed. We
> will be releasing 1.7.3 shortly and it is mostly complet
