One thing I've noticed when I do sudo make install
....
-- Installing: /usr/local/lib/libqpidcommon.so.2.0.0
-- Installing: /usr/local/lib/libqpidcommon.so
-- Removed runtime path from "/usr/local/lib/libqpidcommon.so.2.0.0"
....
-- Installing: /usr/local/lib/libqpidbroker.so.2.0.0
-- Installing: /usr/local/lib/libqpidbroker.so
-- Removed runtime path from "/usr/local/lib/libqpidbroker.so.2.0.0"
....
and a few others of a similar ilk
what on earth does "Removed runtime path from ......" mean?? doesn't
sound good when the library is sitting in /usr/local/lib but when I do
ldd /usr/local/sbin/qpidd I get:
ldd /usr/local/sbin/qpidd
linux-vdso.so.1 => (0x00007fffaefab000)
libqpidbroker.so.2.0.0 => not found
libqpidcommon.so.2.0.0 => not found
libboost_program_options.so.1.46.1 =>
/usr/lib/libboost_program_options.so.1.46.1 (0x00007f496fc9b000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f496f994000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f496f77e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f496f560000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f496f1bd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f496ef39000)
/lib64/ld-linux-x86-64.so.2 (0x00007f496ff2b000)
Frase
On 22/03/13 14:31, Steve Huston wrote:
Can you cd to qpid-trunk/qpid/cpp/bld/src and run qpidd there? May have to set
LD_LIBRARY_PATH to include that dir. The question is why the installed ones
lack 'x' access.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
