I get result from ldd that I don't know how to interpret:
ldd outputs the paths of the shared libraries dynamically linked by an
executable.

I find multiple entries for a given library, viz. one entry with the
original path used at compilation on the development machine - and
which doesn't exist on the target machine- and another with the version
of the library located in the SHLIB_PATH collection of search paths.

Now the application runs, so the path indicated by ldd is not the one
used, so it is presumably using the copy indicated in SHLIB_PATH.

When I use the option "-s" I see that ldd does try the correct
location, but then prints out the original, wrong path.

Does any understand this, and in particular why the application runs?

This behavior is a known defect in the PA32 ldd, which is fixed in a
patch scheduled for release in September 2005. If you want to check
the release notes for it then, it is JAGaf60602 "ldd32 shows paths as
recorded instead of dynamic path search result".

- Carl Burch
HP WDB Team