[slackintosh-users] Re: How to deal with openssl 32/64bit packages
- From: Naveen Nathan <naveen@xxxxxxx>
- To: slackintosh-users@xxxxxxxxxxxxx
- Date: Tue, 31 Oct 2006 23:35:47 -0800
I'm not sure why, but ld just doesn't pickup the 64bit openssl shared
lib unless the openssl-powerpc64 package is installed.
> > Is it actually searching /usr/lib64 aswell? Because shouldn't it pick up
> > on the following:
It does search /usr/lib64, but doesnt pickup /usr/lib64/libssl.so.0:
# strace -eopen ld -m elf64ppc -lssl test.o 2>&1 | grep "/usr/lib64"
open("/usr/lib64/libssl.so", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/lib64/libssl.a", O_RDONLY) = -1 ENOENT (No such file or
directory)
When only the openssl-solibs-powerpc64 package and not
openssl-powerpc64 the libs installed are:
/usr/lib64/libssl.so.0
/usr/lib64/libssl.so.0.9.8
> # ld --version
> GNU ld version 2.15.94.0.2 20041220
I appear to be running the same version.
> Hmm.. does 'ldconfig -p' list the 64bit version of openssl?
It appears to:
root@armakuni:~# ldconfig -p | grep 64bit | grep ssl
libssl.so.0 (libc6,64bit) => /usr/lib64/libssl.so.0
Can't seem to solve this mystery.
Other related posts:
