"Dimitri.p" wrote: > > I haven't seen this message before BUT... > > try this: > ldd will tell you what libraries the executable is trying to access (if > it's dynamically linked) > ie: > ldd somexecutable Will that really work on a foreign binary? I've never tried it. > > If you see references to /shlib or a libary that ordinarily "lives" in > /shlib on the sco box , you'll have to copy these over from an sco box you > already own and you have the license to :) What is the difference between /shlib, /lib, and /usr/lib? I thought they were all shared libs. To be honest, after many t^Hyears of dealing with SCO, I didn't know about /shlib . > > I hope this helps more than confuses :) I have often wondered how iBCS handles dynamically linked executables. I had about decided that it translates the standard (like libc) calls to local equivalents. Is it really just that the SCO binaries I have run are statically linked? Do SCO binaries tend to be static? Linux binaries very much tend to be dynamic. What does this mean for SCO and Solaris, which are (or going to be) providing Linux binary compatability via lxrun, et. al. Will they have to have copies of Linux's shared libs? In closing I must say that it is amusing how quickly things have gone from "But Linux doesn't have any applications." to "Yes! Our OS will run your Linux apps!" ;-) Thanks for any info, -Steve
