On Mon, Dec 17, 2012 at 10:16 AM, Gabriele Bulfon <[email protected]>wrote:
> Hi, > > has anyone any idea how ldd may produce this output on an ".so"? > > -bash-4.0$ ldd _ssl_failed.so > libssl.so.1.0.0 => /lib/libssl.so.1.0.0 > libcrypto.so.1.0.0 => /lib/libcrypto.so.1.0.0 - hardware capability > (CA_SUNW_HW_1) unsupported: 0x4000000 [ AES ] > libpython2.6.so.1.0 => /usr/lib/libpython2.6.so.1.0 > libgcc_s.so.1 => /usr/gcc/4.4/lib/libgcc_s.so.1 > libcrypto.so.1.0.0 => (file not found) > libc.so.1 => /lib/libc.so.1 > libdl.so.1 => /lib/libdl.so.1 > libm.so.2 => /lib/libm.so.2 > > As you can see, the dependency of libcrypto is shown two times, same > verision. > But the second one says "file not found"... > I'm not sure why it would show up twice, but the first one seems to be looking for a version that was compiled for a specific target (looks like a recent Intel CPU with AES-NI extensions). The CPU where this is being loaded doesn't appear to support AES-NI. I've seen this happen in the past when compiling with, e.g. "cc -fast" on an AMD system and attempting to run on an Intel system. Using more generic optimization would be required to support the platforms you appear to be running on. Eric ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
