Console Output:
bitnami@linux:~$ sudo svnmucc propset svn:needs-lock 1 file:///opt/bitnami/repositories/Standard/Ipc/trunk -m "test set"
svnmucc: error while loading shared libraries: libsvn_client-1.so.0: cannot open shared object file: No such file or directory
bitnami@linux:~$ ldd /opt/bitnami/subversion/bin/svnmucc
linux-vdso.so.1 => (0x00007ffee8dfc000)
libsvn_client-1.so.0 => /opt/bitnami/subversion/lib/libsvn_client-1.so.0 (0x00007f3d66102000)
libsvn_wc-1.so.0 => /opt/bitnami/subversion/lib/libsvn_wc-1.so.0 (0x00007f3d65e30000)
libsvn_ra-1.so.0 => /opt/bitnami/subversion/lib/libsvn_ra-1.so.0 (0x00007f3d65c22000)
libsvn_diff-1.so.0 => /opt/bitnami/subversion/lib/libsvn_diff-1.so.0 (0x00007f3d65a09000)
I tried:
"No such file or directory" on an executable, yet file exists and ldd reports all libraries present
I installed:
lib32z1, lib32ncurses5, lib32bz2-1.0
I set:
LD_LIBRARY_PATH="/opt/bitnami/subversion/lib:/opt/bitnami/sqlite/lib:/opt/bitnami/apache2/lib:/opt/bitnami/common/lib"
I am on a -
linux 3.13.0-55-generic #94-Ubuntu x86_64 GNU/Linux
- Bitnami SVN stack. So it is very likely that the Bitnami guys might have cranked something up. Fresh Debian/Arch/Ubuntu is not a solution (Company doesn't want something they can't pay for)
Q: How do I get further? It should have a 64bit 'lib-loader' installed since I am on a 64bit System. svnmucc is further provided by SVN itself, so it should have all libs necessary installed. I would figure that Bitnami somewhat tempered with the System, and now it doesn't have access to it (or something similar). Yet I haven't dealt much with libraries, which is why I am not very well funded in that topic.
export LD_LIBRARY_PATH=/opt/bitnami/subversion/lib
? Is it working after that ? – perror Aug 28 '15 at 12:26LD_DEBUG=libs
in your environment and then running the command. This will trace the library search process. You can setLD_DEBUG=help
to see a list of available debugging options. – larsks Aug 28 '15 at 13:43sudo
tends to clear various environment variables to prevent e.g. some naughty user from loading in a malicious library and then hey presto full superuser access. Are you suresudo
isn't wipingLD_LIBRARY_PATH
? – thrig Aug 28 '15 at 14:36