Re: [OMPI users] unable to open osc pt2pt

This should be fixed in the subversion trunk of mpi4py. Can you do an update to that version and retry. If it still doesn't work, post to the mpi4py list and we will see what we can do. Brian On Dec 17, 2007 8:25 AM, de Almeida, Valmor F. wrote: > > Hello, > > I am getting these messages (belo

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

andro and see what he thinks though. If you don't hear back from us within a day, assume everything is fine. Brian On Dec 10, 2007 10:13 AM, Jeff Squyres wrote: > On Oct 16, 2007, at 11:20 AM, Brian Granger wrote: > > > Wow, that is quite a study of the different options. I wi

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

On 10/16/07, Jeff Squyres wrote: > On Oct 16, 2007, at 11:20 AM, Brian Granger wrote: > > > Wow, that is quite a study of the different options. I will spend > > some time looking over things to better understand the (complex) > > situation. I will also talk with Lisan

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

changed in this respect from 1.2.3 to 1.2.4, but 1.2.3 doesn't show the problem. Does this make sense? Brian On 10/16/07, Jeff Squyres wrote: > On Oct 12, 2007, at 3:5 PM, Brian Granger wrote: > > > My guess is that Rmpi is dynamically loading libmpi.so, but not > > > speci

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

> My guess is that Rmpi is dynamically loading libmpi.so, but not > specifying the RTLD_GLOBAL flag. This means that libmpi.so is not > available to the components the way it should be, and all goes > downhill from there. It only mostly works because we do something > silly with how we link most

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

> That's the same for R. We don;t touch the innert guts of module loading for > this . What Hao realized after looking at the corresponding FAQ item was that > right before calling MPI_Init, one can load libmpi explicitly, and -- and > that;s the important bit -- set the proper RTLD_GLOBAL argument

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

I am seeing the same error, but I am using mpi4py (Lisandro Dalcin's Python MPI bindings). I don't think that libmpi.so is being dlopen'd directly at runtime, but, the shared library that is linked at compile time to libmpi.so is probably being loaded at runtime. The odd thing is that mpi4py has

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

I should say that on FC5, where I see the error, mpi runs just fine. Brian On 10/9/07, Dirk Eddelbuettel wrote: > > On 8 October 2007 at 22:06, Brian Granger wrote: > | Also seeing this problem on Fedora Core 5. Any resolution yet? > > No, none. With the exact same configurat

Re: [OMPI users] Open MPI 1.2.4 verbosity w.r.t. osc pt2pt

Also seeing this problem on Fedora Core 5. Any resolution yet? Brian On 10/6/07, Dirk Eddelbuettel wrote: > > On 6 October 2007 at 09:36, Dirk Eddelbuettel wrote: > | > | On 5 October 2007 at 21:31, Brian Barrett wrote: > | | On Oct 5, 2007, at 8:48 PM, Dirk Eddelbuettel wrote: > | | > | | > Wi

Re: [OMPI users] mpi python recommendation

mpi4py has emerged as the best python mpi bindings. It has the best coverage of the mpi spec, the best test coverage and has fantastic performance: http://www.cimec.org.ar/ojs/index.php/cmm/article/view/8/11 Brian On 6/20/07, de Almeida, Valmor F. wrote: Hello list, I would appreciate rec

[OMPI users] Dynamic loading of libmpi.dylib on Mac OS X

valid MCA components. -- [localhost:00973] PML ob1 cannot be selected Any Ideas? Thanks Brian Granger

[OMPI users] Dynamically loading mpi on Mac OS X

3] PML ob1 cannot be selected Any Ideas? Thanks Brian Granger

Re: [O-MPI users] Configuring OPEN MPI 1.0.1 MAC OS X 10.4.4

Hi, It looks like it could be a problem with either using gcc 4.x or with the fortran you are using. I have compiled OpenMPI on 10.4.4. using the compilers: myhost$ g77 -v Reading specs from /usr/local/lib/gcc/powerpc-apple-darwin7.9.0/3.4.4/ specs Configured with: ../gcc/configure --ena

Re: [O-MPI users] Configuring process startup on OS X

Brian, Excellent. This definitely gives me enough information to get going. I will give feeback as I try it out. Brian On Jan 30, 2006, at 5:44 AM, Brian Barrett wrote: On Jan 29, 2006, at 6:09 PM, Brian Granger wrote: I have compiled and installed OpenMPI on Mac OS X. As I

Re: [O-MPI users] Bug in C++ bindings

OK, Thanks for looking into this. Brian On Feb 1, 2006, at 8:05 AM, Brian Barrett wrote: On Jan 31, 2006, at 5:47 PM, Brian Granger wrote: I am compiling a C++ program that uses the Open-MPI c++ bindings. I think there is a bug in the constants.h and/or mpicxx.cc files. The file

[O-MPI users] Bug in C++ bindings

owing constants: not defined in mpicxx.cc: ERR_COUNT SIGNED_CHAR only defined in mpicxx.cc if one-sided support is enabled: WIN_NULL By commenting corresponding lines out in constants.h, my code compiled and ran fine. Is this a bug, or should these things be defined somewhere else. Thanks!

[O-MPI users] Configuring process startup on OS X

pointers about where to look for more documentation? Thanks, Brian Brian Granger, Ph.D. Assistant Professor of Physics Santa Clara University bgran...@scu.edu Phone: 408-551-1891 Fax: 408-554-6965 This message scanned for viruses and SPAM at SCU (MGW2)