I wonder, if there is a way to display library dependencies of
an executable or shared object, when "ldd" does not work.
Specifically, it is often necessary to find out, what library
and where the loader is looking for, when it is _not_ finding
it. If the rpath has been recorded to an executable, there
_should_ be some way to dig out the information.
ldd is of no use in such a situation, because it also complains
about missing libraries, unlike on some other systems, where it
tells the missing library name among others. I also looked at
"odump", but did not find anything useful in it either.
In the same vein, ldd also seems to have problems with objects,
that have been "spiked", i.e. optimized with spike. If applied
on many such objects, ldd dumps core with segmentation fault,
but not always.
A third strange property of ldd: if you invoke it in KDE2 "konsole",
the effect is the same as typing "exit" on the prompt! Strange...
It works properly on an xterm, though.
The systems I've been trying these are running either Tru64 5.1 PK2
or 4.0G PK1 and PK2.
ArNO
2
Received on Mon Mar 05 2001 - 14:35:05 NZDT