Hi,
thank you very much for fixing the bug so fast. I can compile
openmpi-1.7.3a1r29220 and it seems that it works. I will do some more
tests on Monday.
Kind regards
Siegmar
> I tried to install openmpi-1.7.3a1r29213 on "openSuSE Linux 12.1",
> "Solaris 10 x86_64", and "Solaris 10 sparc" with
Hi,
today I installed 32- and 64-bit versions of openmpi-1.7.3a1r29220 on
Solaris Sparc with Sun C 5.12 and gcc.4.8.0. "make check" has the
following problem with both versions and both compilers.
"make check" works fine with "openmpi-1.6.6a1r29175".
tyr openmpi-1.7.3a1r29220-SunOS.sparc.64_gcc 1
Can uu send a stack trace from the failed DDT-raw test?
Sent from my phone. No type good.
On Sep 21, 2013, at 10:05 AM, "Siegmar Gross"
wrote:
> Hi,
>
> today I installed 32- and 64-bit versions of openmpi-1.7.3a1r29220 on
> Solaris Sparc with Sun C 5.12 and gcc.4.8.0. "make check" has the
>
Any Suggestions
From: basmaabdelaz...@hotmail.com
To: us...@open-mpi.org
Subject: FT problem
Date: Wed, 18 Sep 2013 16:42:29 +0200
i am using openmpi-1.6.1
i need to try checkpoint restart ( self , blcr )
after i installed openmpi i had the following in my installation folder :
bin\ ompi-ch
Hello Jeff,
> Can uu send a stack trace from the failed DDT-raw test?
Here is the output from gdb.
tyr .libs 41 ddt_raw
#
* TEST INVERSED VECTOR
#
Bus error (core dumped)
tyr .libs 42 gdb ddt_raw core
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered
Hi,
today I build openmpi-1.6.6a1r29175 with Sun C 5.12 and gcc-4.8.0
on Linux. Unfortunately "make check" hangs.
linpc1 openmpi-1.6.6a1r29175-Linux.x86_64.32_cc 138
tail log.make-check.Linux.x86_64.32_cc
"../../../openmpi-1.6.6a1r29175/opal/include/opal/sys/atomic_impl.h",
line 165: warnin
Hi,
today I build openmpi-1.7.3a1r29220 with Sun C 5.12 and gcc-4.8.0
on Linux. Unfortunately "make check" hangs.
linpc1 openmpi-1.7.3a1r29220-Linux.x86_64.32_cc 108
tail log.make-check.Linux.x86_64.32_cc
CCLD opal_path_nfs
make[3]: Leaving directory
`/export2/src/openmpi-1.7/openmpi-1.
Not really - the person who wrote that code for his PhD thesis has since become
a professor and rarely has time to respond on the mailing list, nor to maintain
the code. So I'm afraid we don't have anyone who knows much about it any more.
I plan to rework the checkpoint support in upcoming month
