On Thu, 2014-03-13 at 10:46 -0700, Ross Boylan wrote:
>
> It seems very odd that the same Rmpi.so is requiring both the old and
> new libmpi.so (compare to the first
> trace in in point 1). There is this code in Rmpi.c:
> if (!dlopen("libmpi.so.0", RTLD_GLOBAL | RTLD_LAZY)
> && !dlop
On Thu, 2014-03-13 at 10:46 -0700, Ross Boylan wrote:
> 1. My premise that R had no references to mpi was incorrect. The logs
> show
> 24312: file=libmpi.so.1 [0]; needed
> by /home/ross/Rlib-3.0.1/Rmpi/libs/Rmpi.so [0]
> 24312: find library=libmpi.so.1 [0]; searching
> 24312:
@r-project.org [mailto:r-devel-boun...@r-project.org] On
> Behalf
> Of Ross Boylan
> Sent: Wednesday, March 12, 2014 10:01 PM
> To: Simon Urbanek
> Cc: r-devel@r-project.org
> Subject: Re: [Rd] 2 versions of same library loaded
>
> Comments/questions interspersed below.
&g
Comments/questions interspersed below.
On Wed, 2014-03-12 at 22:50 -0400, Simon Urbanek wrote:
> Ross,
>
> On Mar 12, 2014, at 5:34 PM, Ross Boylan wrote:
>
> > Can anyone help me understand how I got 2 versions of the same library
> > loaded, how to prevent it, and what the consequences are? R
Ross,
On Mar 12, 2014, at 5:34 PM, Ross Boylan wrote:
> Can anyone help me understand how I got 2 versions of the same library
> loaded, how to prevent it, and what the consequences are? Running under
> Debian GNU/Linux squeeze.
>
> lsof and /proc/xxx/map both show 2 copies of several librarie
Can anyone help me understand how I got 2 versions of the same library
loaded, how to prevent it, and what the consequences are? Running under
Debian GNU/Linux squeeze.
lsof and /proc/xxx/map both show 2 copies of several libraries loaded:
/home/ross/install/lib/libmpi.so.1.3.0
/home/ross/install
