similar to: LD_LIBRARY_PATH is harmfull

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

Hi, I have seen the bug http://llvm.org/bugs/show_bug.cgi?id=896 Maybe it is a non-issue but I had some trouble with this. I am running Debian sid and were no longer able to compile llvm. /home/fred/llvm/build/gcc/xgcc: /home/fred/llvm/build/gcc/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) The installed version have this symbol. strings

This change allows the run scripts of virt-v2v and libguestfs to be chained. --- run.in | 16 +++++++++++++--- 1 files changed, 13 insertions(+), 3 deletions(-) diff --git a/run.in b/run.in index 9388398..7cef715 100755 --- a/run.in +++ b/run.in @@ -37,9 +37,19 @@ b=@abs_builddir@ export TMPDIR="$b" # Set local environment relative to this script. -export

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

Well, I've found that the line in INSTALL that gives the problem is gzip -dc "${1}" | (cd "${tmpdir}" && tar -xf -) ("tar: /usr/local/lib/libpthread.so.0: version `GLIBC_2.2' not found (required by /lib/librt.so.1)") If I run that command from the shell, i.e., gzip -dc KernSmooth_2.22-7.tar.gz | (cd /tmp/R.INSTALL.2186 && tar -xf -) it runs

Overwriting LD_LIBRARY_PATH broke some tests when running with fakeroot. --- align/Makefile.am | 2 +- cat/Makefile.am | 2 +- clone/Makefile.am | 2 +- df/Makefile.am | 2 +- edit/Makefile.am | 2 +- fish/Makefile.am | 2 +- haskell/Makefile.am | 2 +- ocaml/Makefile.am |

Dear R-help, I am trying to use a package (not from CRAN) which includes two shared library (.so) files. The maintainer suggests inserting two lines in /usr/bin/R, LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:path-to-package/lib export LD_LIBRARY_PATH This works, but I felt more comfortable putting the first line in .Renviron or $R_HOME/etc/Renviron.site. However this doesn't seem to work, and I

Hello, I have a CentOS 5.5/64bit VM, where I only have sudo rights: afarber ALL=(ALL) NOPASSWD: ALL I'm trying to pass LD_LIBRARY_PATH through sudo to install DBD::Oracle ( https://rt.cpan.org/Ticket/Display.html?id=63678 ) and have tried using "sudo -E" and also changing these lines in the stock /etc/sudoers: Defaults !env_reset Defaults env_keep =

Hi all, Just noted this behavior in the past couple of days, where if R is started in a shell script such as: gnome-terminal [-e][-x] R or in ESS (version 5.2.12 with Emacs or XEmacs), the LD_LIBRARY_PATH environment variable is not properly appended to, resulting in the loss of the pre-start value. This is using R Version 2.2.1 Patched (2006-02-28 r37448) on FC4. I noted this when

Hi! I ran into a problem with programs exec:ed by print/acroread8 picking up Linux libraries and thus failed to run. This includes the print program in the print dialogue and the browser configured in edit/preferences/internet. The reason is that the acroread launch script sets LD_LIBRARY_PATH which is propagated to its childs. See this PR:

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

Hello, I'm trying to get the LD_LIBRARY_PATH set from .bash_profile (Centos 5.3 fully updated). This is a part of my .bash_profile: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/szyman/omnet/omnetpp-2.3p1/lib export R_HISTSIZE=2000000000 Everything works fine under standard ssh login, but under NX client the LD_LIBRARY_PATH variable is missing (the R_HISTSIZE is exported properly). Any

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

I am writing an R package to interface to hdf5 files (yes I know one exists, the issue will be demonstrated using that package). I tend to like to build/install things locally so that aspects of the system I am working on don't cause problems later when attempting to install elsewhere. To this end, I build and install the hdf5 libraries w/out incident: tar xzf hdf5-1.8.4.tar.bz2 cd hdf5-1.8.4

On Thu, 19 Jul 2007, Reid Spencer wrote: > With the pending reorganization of the software, I have some questions > about how developers set their PATH and LD_LIBRARY_PATH variables when > working with LLVM. This is a bit long winded, but bear with me. ok :) > We're planning to break the "llvm" module up into three modules: > > * support - lib/Support,

Hi, i am getting an issue with rtorrent that is related to my curl libaries. In summary it requires a later curl libary than CentOS 5.4 uses for its system files (CentOS uses curl libs version 7.15.5, rtorrent requires 7.19.2 or greater). To get around this I would like to download the latest curl version and compile and link to rtorrent without affecting system files. How can i statically

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

All, With the pending reorganization of the software, I have some questions about how developers set their PATH and LD_LIBRARY_PATH variables when working with LLVM. This is a bit long winded, but bear with me. We're planning to break the "llvm" module up into three modules: * support - lib/Support, lib/System, autoconf, make support, utilities * core - VMCore,

Hi All, finally, I've got time and resources for development. Unfortunately I couldn't afford playing with my UPS because it was used permanently, but now it's ok. I've checked out cureent trunc and I see that Andrey Lelikov's changes haven't been applied yet. What's wrong with them? I think, he made a great job to simplify future support for this kind of

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,