schoch@trident.arc.nasa.gov (Steve Schoch) (10/08/90)
Given that an object file resides in a .so file and an archive, both specified in an ld step with the .so file specified first, is there any reason that ld would resolve a reference from the archive instead of the .so shared object? Is it a problem with the reference somehow not "global" and therefore not seen by the loader? The shared object is being create just like specified in Chapter 1 - Shared Libraries in the Programming Utilities and Libraries manual. A "-M" on the ld step doesn't help much; it doesn't list the reason a particular .so was pulled in. dueker@xenon.arc.nasa.gov | Chris Dueker (The Code Slinger) chris@chuck.arc.nasa.gov | Mtn. View, CA (Sillycon Valley!)