in reply to Crypt::SSLeay problem after upgrading to 5.10
I agree with eserte, but if you can't or don't want to wait until the dependency issue is fixed, you could - as a temporary solution - try to build openssl (libssl) from the sources yourself and put it under /usr/local. (You might or might not need to build zlib as well.) Then, once the deb package issue is sorted out, you would simply rebuild the Perl module the way you tried it now, and delete the temp stuff in /usr/local.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Crypt::SSLeay problem after upgrading to 5.10
by jkeenan1 (Deacon) on Dec 21, 2007 at 19:02 UTC | |
Jim Keenan
| [reply] [d/l] |
by almut (Canon) on Dec 21, 2007 at 23:02 UTC | |
cc -c -I/usr/local/ssl/include/openssl -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"0.57\" -DXS_VERSION=\"0.57\" -fPIC "-I/usr/local/lib/perl5/5.10.0/i686-linux/CORE" SSLeay.c In file included from SSLeay.xs:25: crypt_ssleay_version.h:1:25: error: openssl/ssl.h: No such file or directory It doesn't find the header(s) because it's looking in /usr/local/ssl/include/openssl/openssl/ssl.h — i.e. one openssl path fragment too much. (The relative path fragment from the #include "openssl/ssl.h" directive is simply being appended to any search paths specified via -I) It's probably easiest to just move the openssl include directory into /usr/local/include, as that's already specified on the compiler's command line (-I/usr/local/include). | [reply] [d/l] [select] |
by jkeenan1 (Deacon) on Jan 07, 2008 at 19:34 UTC | |
Jim Keenan
| [reply] [d/l] |