similar to: setting LD_LIBRARY_PATH

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/lib/libopen-pal.so.6.1.0 /home/ross/install/lib/libopen-rte.so.7.0.0

Hello! I'm trying to install R-3.0.1 on an Ubuntu machine (64 bit, version 13.04). I have uninstalled and installed several times, but to no avail. I keep getting errors about missing ldpaths, and installing packages does not work at all. Here is the information: erin@erin-Lenovo-IdeaPad-Y480:~$ sudo apt-get install r-base Reading package lists... Done Building dependency tree Reading

Hi all, I've just upgraded my old Solaris 10 update 8 to Solaris 10 update 11 with the latest patches, but after the reboot with the new update I'm having a lot of problems with dovecot. My version is 2.2.13 ( it was the last one, at the time of the first server setup ). I have seen that ( it seems ) the new solaris don't honour the LD_LIBRARY_PATH. The first error was a

Using R-2.8.0 and R-2.8.1, I get behaviour like this: R version 2.8.0 (2008-10-20) Copyright (C) 2008 The R Foundation for Statistical Computing ISBN 3-900051-07-0 [....] > Sys.getenv("LD_LIBRARY_PATH") LD_LIBRARY_PATH

I've got a situation where I need to hook a dlopen() made by VDDK, a proprietary library, where it passes a relative name expecting to resolve to a copy of several libraries, including libstdc++.so, that it installs alongside itself, and fails to load if that resolves to the system libstdc++.so. The simplest solution of providing LD_LIBRARY_PATH is enough to load VDDK, but then poisons

On Fri, Feb 21, 2020 at 01:19:34PM +0100, Florian Weimer wrote: > I think what confuses me is that keep talking about a single binary, but > clearly there is this separate vddk DSO, and there is talk of plugins. > So it seems to me that multiple files are involved already? nbdkit is a standalone binary that happens to be able to load plugins from a well-known path, eg

When using R on a linux machine (ubuntu 8.10) which DOES NOT have LD_LIBRARY_PATH set (I particularly have it NOT set because it causes problems), the script ldpaths will set LD_LIBRARY_PATH to the R Lib path (in my case $R_HOME/lib:). The placement of the colon makes my system think that the directory "." is also on that lib path. This causes real problems when trying to run R

Answer inline. On Sun, Dec 30, 2018 at 12:59 PM James <list at xdrv.co.uk> wrote: > On 29/12/2018 13:49, Pierluigi Frullani wrote: > > > My version is 2.2.13 ( it was the last one, at the time of the first > > server setup ). > > 2.2.13 is from around May 2014. It worked but I can't see why you > wouldn't switch to the latest 2.3.4. (You might be seeing

On Fri, Feb 21, 2020 at 04:00:30PM +0100, Florian Weimer wrote: > * Richard W. M. Jones: > > > On Fri, Feb 21, 2020 at 01:19:34PM +0100, Florian Weimer wrote: > >> I think what confuses me is that keep talking about a single binary, but > >> clearly there is this separate vddk DSO, and there is talk of plugins. > >> So it seems to me that multiple files are

Hi everyone, Two minor points about ?.Renviron. 1) If R_ENVIRON is not set then R defaults to `${R_HOME}/etc/Renviron', not `${R_HOME}/etc/Renviron.site' as stated. 2) In the details, there is a missing "way" in "`value' is processed in a similar to a Unix shell." Cheers, Jonathan. --please do not edit the information below-- Version: platform =

Dear all, When installing the usual packages that I use, after installing R 3.0.1, I noticed that the installation of some packages that query R about its configuration did not succeed. The problem is exemplified by: berwin at bossiaea:~$ R-3.0.1 CMD config CC /opt/R/R-3.0.1/lib/R/bin/config: 222: .: Can't open /opt/R/R-3.0.1/lib/R/etc/Renviron Prior to R 3.0.1 such commands worked fine:

On 2/17/20 9:12 AM, Florian Weimer wrote: > * Eric Blake: > >> I'm just now noticing that 'man ld' reports that you may pass '--audit >> LIB' during linking to add a DT_DEPAUDIT dependency on a library >> implementing the audit interface, which sounds like it might be an >> alternative to LD_AUDIT for getting a library with la_objsearch() to

Hi, I am interested in customizing the installation of R. I have gone through the ?R Installation and Administration? manual. But some of the stuff is not clear to me and I would like to get clarifications on the following points (for a Windows installation with R_HOME=C:\\R\\R-2.9.1 ) : 1. I understand that I need to create a file, .Renviron with the following path : R_HOME\\etc\\.Renviron where

On 2/14/20 3:29 PM, Eric Blake wrote: > On 2/14/20 1:02 PM, Eric Blake wrote: > >> Writing my own dlopen() wrapper directly in nbdkit seems like a >> non-starter (my override has to come from a shared library before it >> can replace the shared version that would be imported from -ldl, at >> least for all subsequent shared library loads that want to bind to the

Here is the thing. All workstations in the network have the /etc/profile modified and set up to call a profile script in the network that sets up variables that we need here. Here $LD_LIBRARY_PATH and other variables get set, fixed, or modified to support our development process. The weird thing is that while in a TTY the $LD_LIBRARY_PATH is fine and retains its value. But if I log in to the gui

On Fri, Feb 21, 2020 at 05:02:12PM +0100, Florian Weimer wrote: > * Richard W. M. Jones: > > > On Fri, Feb 21, 2020 at 04:00:30PM +0100, Florian Weimer wrote: > >> * Richard W. M. Jones: > >> > >> > On Fri, Feb 21, 2020 at 01:19:34PM +0100, Florian Weimer wrote: > >> >> I think what confuses me is that keep talking about a single binary,

On 07/30/2014 10:06 AM, Larry Evans wrote: > On 07/30/2014 12:35 AM, Ben Pope wrote: >> On Wednesday, July 30, 2014 01:31 PM, Ben Pope wrote: >> >>> ldd your_built_clang | grep libstdc++ >>> chrpath -l your_built_clang >> >> Hmm, where "your_built_clang" should be the actual failing executable: >>

I am having difficulty coming to grips with Appendix B.2 of the otherwise very useful "An Introduction to R" and the related help file for Startup. I am running RGui 1.6.0 on a Windows 2000 machine from the default installation. How the concepts discussed in B.2 and the Startup help file relate to what I see on my machine is something of a mystery. I quote from the Startup file:

Mac OS X uses DYLD_LIBRARY_PATH rather than LD_LIBRARY_PATH. --- run.in | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/run.in b/run.in index a8c2904..bf7ea1b 100755 --- a/run.in +++ b/run.in @@ -77,13 +77,10 @@ fi

First I tried 'setenv R_SHELL /usr/local/bin/bash', as bash is the weapon of choice for the faculty wishing to use R, then ran ./configure as before. The ./configure output line using as R_SHELL for scripts ... /usr/local/bin/bash would seem to indicate that the R_SHELL environment variable was recognized and acknowledged. However, I got the same build error: gnumake[2]: Entering