On 13 December 2007 at 13:17, Lisandro Dalcin wrote:
| Perhaps I was not clear enough. There are many public ways of
| importing modules in Python. Modules can came mainly from two sources:
| pure Python code, or C compiled code. In the later case (called
| extension modules), they are normally a
On Dec 13, 2007, at 6:01 PM, Brian W. Barrett wrote:
But it is easy for OPen MPI to figure out whether it's statically or
dynamically linked, as libtool compiles the code twice if building
both
static and shared and you could poke at #defines to figure out what's
going on -- easy enough to de
I installed OpenMPI-1.2.4 on our cluster.
Here is the compute node infor
[qiang@compute-0-1 ~]$ uname -a
Linux compute-0-1.local 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006
i686 i686 i386 GNU/Linux
[qiang@compute-0-1 bin]$ gcc -v
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/
I have found that on rare occasion Allgatherv fails to pass the data to
all processes. Given some magical combination of receive counts and
displacements, one or more processes are missing some or all of some
arrays in their receive buffer. A necessary, but not sufficient,
condition seems to be t
On Wed, 12 Dec 2007, Alex Pletzer wrote:
I'm on a AMD64 box (Linux quartic.txcorp.com 2.6.19-1.2288.fc5 #1 SMP
Sat Feb 10 14:59:35 EST 2007 x86_64 x86_64 x86_64 GNU/Linux) and
compiled openmpi-1.2.4 using the Lahey-Fujitsu compiler (lfc). The
compilation of openmpi went fine.
$ ../configure --
On Thu, 13 Dec 2007, Jeff Squyres wrote:
Specifically: it would probably require some significant hackery in
the OMPI build process to put in a #define that indicates whether OMPI
is being built statically or not. But the AM/LT process shields this
information from the build process by design (
I solved the problem and the quote 'we have met the enemy and he is
us' fits prefectly.
The reason was I had a stale object file laying around from when i
used a different compiler. Removing mpif.h as they are listed in the
PARPACK ARmake.inc and recompiling worked.
Sorry for the red her
If you want to use the pessimist message logging you have to use the "-
mca vprotocol pessimist" flag on your command line. This should work
despite the bug because if I understand correctly, the issue you
experience should occur only when fault tolerance is disabled.
I have troubles to reprod
On 12/13/07, Jeff Squyres wrote:
> On Dec 12, 2007, at 7:47 PM, Lisandro Dalcin wrote:
> Specifically: it would probably require some significant hackery in
> the OMPI build process to put in a #define that indicates whether OMPI
> is being built statically or not. But the AM/LT process shields t
Excellent. Thanks.
-Ken
> -Original Message-
> From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
On
> Behalf Of Jeff Squyres
> Sent: Thursday, December 13, 2007 6:02 AM
> To: Open MPI Users
> Subject: Re: [OMPI users] Problems with GATHERV on one process
>
> Correct.
On Dec 12, 2007, at 1:18 PM, Warner Yuen wrote:
It seems that the problems are partially the compilers fault, maybe
the updated compilers didn't catch all the problems filed against
the last release? Why else would I need to add the "-no-multibyte-
chars" flag for pretty much everything that
On Dec 12, 2007, at 7:47 PM, Lisandro Dalcin wrote:
You should, yes.
OK, but now I realize that I cannot simply call libtool dlopen()
inconditionally, as libmpi.so could not exist in a static lib build.
Right. Or it could be libmpi.dylib (OS X). I don't know if other
extensions exist out
Correct. Here's the original commit that fixed the problem:
https://svn.open-mpi.org/trac/ompi/changeset/16360
And the commit to the v1.2 branch:
https://svn.open-mpi.org/trac/ompi/changeset/16519
On Dec 12, 2007, at 2:43 PM, Moreland, Kenneth wrote:
Thanks Tim. I've since noticed
I still have the same error after update (r16951).
I have the lib/openmpi/mca_pml_v.so file in my builld and the command
line I use is: mpirun -np 4 my_application
Thomas
Aurelien Bouteiller wrote:
I could reproduce and fix the bug. It will be corrected in trunk as
soon as the svn is onlin
Brian raised a good point -- your project must already have a portable
solution for dlopen() since it's loading your plugin.
Can you not use that?
On Dec 12, 2007, at 8:40 AM, Jeff Squyres wrote:
On Dec 11, 2007, at 9:08 AM, Lisandro Dalcin wrote:
(for a nicely-formatted refresher of the
15 matches
Mail list logo
