Sundara Vardhan wrote: > When I used -Bstatic -lfsu ... etc I expected that libfsu.a to be used to > staticall link to my application. However, in runtime, I found that the > application barfed looking for libfsu.so...
There's a lengthy description of library processing following the "Input File Processing" section of the Linker and Libraries Guide: http://docs.sun.com/app/docs/doc/817-1984/6mhm7pl16?a=view Perhaps you have linked against libfsu.a and other shared objects, and it is one of these other shared objects that has its own dependency on libfsu.so. You can determine what libraries the link-editor is processing with: % LD_OPTIONS=-Dlibs,files,detail cc -o main .... -Bstatic -lfsu ... And, you can determine where all runtime dependencies originate from: % ldd -rs main Perhaps, with these methods of observing things, you can unravel what's going on. -- Rod
