[Andy Polyakov] > Both pa-risc and ia64 linkers look for both .so and .sl and once program > is linked with some shared object it will require that particular one. > And at run-time shared object extension has no meaning whatsoever, it's > the contents matching ABI for current process, which determines if any > particular file is successfully loaded to address space.
True. But this creates problem when compiling on one host, and distributing the binaries into other hosts. > Can you present evidence that it's not [in OpenSSL context]? A. I discovered this problem because some of our hppa binaries had been distributed to our ia64 binaries, which also had ia64 openssl libraries with .sl extentions. These libraries were used instead of the correct hppa libraries, and the binaries broke. (This is a long time ago, so I do not remember the details.) You might argue that our setting is very special, but it is a real one. We maintain ~1700 unix machines the largest university in Norway, and discovered the problem when we introduced hp-ux/ia64 machines. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
