On Feb 5, 2010, at 1:28 PM, Merker, Nick wrote:
> I am receiving errors when compiling Crypt::SSLeay on RHEL4ASu7 x86_64.
^^^^^^
64bits system...
> $ make test
> # Error: Can't load
> '/home/nmerker/.cpan/build/Crypt-SSLeay-0.57/blib/arch/auto/Crypt/SSLeay/SSLeay.so'
> for module Crypt::SSLeay:
> /home/nmerker/.cpan/build/Crypt-SSLeay-0.57/blib/arch/auto/Crypt/SSLeay/SSLeay.so:
> cannot open shared object file: No such file or directory at
> /usr/local/cars-perl/5.8.8/lib/5.8.8/i686-linux/DynaLoader.pm line 230.
^^^^^^^^^^^
That looks like a 32bits Perl... run file /usr/local/cars-perl/bin/perl ?
>
> I am fairly certain this is something to do with being unable to load
> libcrypto.so or libssl.so, so I checked it out:
> # ldd
> /home/nmerker/.cpan/build/Crypt-SSLeay-0.57/blib/arch/auto/Crypt/SSLeay/SSLeay.so
> libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a9566a000)
> /lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000)
That seems like a 64bits build, but file can tell you.
A 32bits binary cannot load a 64bits library. I'd say building a 64bits Perl,
or 32bits Perl modules on a 64bits system, is off-topic for this list.
S.
> That looks fine. I have the following packages installed:
> openssl-0.9.7a-43.17.el4_6.1
> openssl-devel-0.9.7a-43.17.el4_6.1
>
> I am confused as to what is missing here. From my standpoint, there should
> be no error when trying to load SSLeay.so file, especially a “No such file or
> directory” error because ‘ldd’ responds properly.
>
> What am I missing here?
>
> -Nick
--
san...@temme.net http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
smime.p7s
Description: S/MIME cryptographic signature
