An additional way to debug is to use dump -H of the executable as well as the libraries.
Seeing the output of the program when it fails is also useful for debugging. You need to read the error message carefully as it tells you which member it is loading and that member cannot find a dependency - and which dependency iit is missing.
Or have you solved this already?
If so, please share your solution!
---------- Post updated at 12:33 PM ---------- Previous update was at 12:18 PM ----------
Errr... Preview threw it all away. So, short version.
ofsrm <> testExe
Based on the error message I would compare dump -H of the following files:
- ofsrm
- testExe
- /build1/build/SourcePro/ficdb/lib/libFSGBU/libaccess.a
Probably, the last (the archive) does not have an accurate library search path.