I'm trying to get a certain unprintable source code control system running here on my Debian box.

LD_LIBRARY_PATH is:
/usr/local/dev/pvcs/vm/linux/lib/linux/native_threads:/usr/local/dev/pvcs/vm/linux/bin

/usr/local/dev/pvcs/vm/linux/lib/linux/native_threads is also in my ld.so.conf (and ldconfig has been run; everything in that directory can be seen in ld.so.cache).

Running this POS gives me the following:

libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory (libpvcsjvms.so)
Cannot load VMS: "no pvcsjvms in shared library path"

libpvcsjvms.so is in /usr/local/dev/pvcs/vm/linux/lib/linux/native_threads, of course. I've also tried linking everything in that directory into /usr/lib (and /lib, as well) based on something I found on the Merant knowledge base site:

The Version Manager shared libraries are built with the default search path embedded into the libraries as well as the executables. This search path is the default installation path that is recommended during product installation. Example: (Solaris search path would be - /usr/pvcs/vm/solaris/lib/sparc/native_threads). It is important to note that the primary search path is the default installation path and the secondary search path is /usr/lib. If the shared libraries cannot be found in either location the OS will perform a core dump. There are a few exceptions to this behavior and they will be noted below.

Unfortunately, Linux isn't one of the OSes listed. Also, this note is in reference to running in setuid mode, which I'm pretty sure it isn't.

Any ideas?

Re: running ldconfig: yep. I believe I mentioned that as well. ;-)

Re: compat libs: I only vaguely know what that is. However, the lib it's looking for comes with the software installation, so it's not a Linux lib that's missing.

I've managed to get a few of the command line utilities to run by doing an explicit 'export LD_LIBRARY_PATH=etc' before running the command. I can't seem to make it "stick", however.

There are other command line apps which appear to start up other apps under a different environment. I think I'm just going to have to wade down through their shell scripts and figure out if LD_LIBRARY_PATH is being carried along for the ride.

Now, to fix it. :-P