On Mar 13, 2014, at 3:15 PM, Ross Boylan wrote:
> The motivation was
> http://www.stats.uwo.ca/faculty/yu/Rmpi/changelogs.htm notes
> --
> 2007-10-24, version 0.5-5:
>
> dlopen has been used to load libmpi.so explicitly. This is mainly useful
> for Rmpi under Open
On Wed, 2014-03-12 at 10:52 -0400, Bennet Fauber wrote:
> My experience with Rmpi and OpenMPI is that it doesn't seem to do well
> with the dlopen or dynamic loading. I recently installed R 3.0.3, and
> Rmpi, which failed when built against our standard OpenMPI but
> succeeded using the following
On Wed, 2014-03-12 at 14:34 +, Dave Goodell (dgoodell) wrote:
> Perhaps there's an RPATH issue here? I don't fully understand the structure
> of Rmpi, but is there both an app and a library (or two separate libraries)
> that are linking against MPI?
>
> I.e., what we want is:
>
> app -
I remember having a conversation with someone from R at Supercomputing last
year, and this was one of the issues we discussed. The problem is that you have
to ensure that R is built against the OMPI you are going to use, and it is
usually better to have configured OMPI --disable-dlopen --enable-
On Wed, 2014-03-12 at 11:50 +0100, Reuti wrote:
> Am 12.03.2014 um 11:39 schrieb Jeff Squyres (jsquyres):
>
> > Generally, all you need to ensure that your personal copy of OMPI is used
> > is to set the PATH and LD_LIBRARY_PATH to point to your new Open MPI
> > installation. I do this all the
My experience with Rmpi and OpenMPI is that it doesn't seem to do well
with the dlopen or dynamic loading. I recently installed R 3.0.3, and
Rmpi, which failed when built against our standard OpenMPI but
succeeded using the following 'secret recipe'. Perhaps there is
something here that will be h
Perhaps there's an RPATH issue here? I don't fully understand the structure of
Rmpi, but is there both an app and a library (or two separate libraries) that
are linking against MPI?
I.e., what we want is:
app -> ~ross/OMPI
\ /
--> library --
But what we'r
Am 12.03.2014 um 11:39 schrieb Jeff Squyres (jsquyres):
> Generally, all you need to ensure that your personal copy of OMPI is used is
> to set the PATH and LD_LIBRARY_PATH to point to your new Open MPI
> installation. I do this all the time on my development cluster (where I have
> something
Generally, all you need to ensure that your personal copy of OMPI is used is to
set the PATH and LD_LIBRARY_PATH to point to your new Open MPI installation. I
do this all the time on my development cluster (where I have something like 6
billion different installations of OMPI available... mmm..
I took the advice here and built a personal copy of the current openmpi,
to see if the problems I was having with Rmpi were a result of the old
version on the system.
When I do ldd on the relevant libraries (Rmpi.so is loaded dynamically
by R) everything looks fine; path references that should be
10 matches
Mail list logo
