Skip Menu |

This queue is for tickets about the Crypt-SSLeay CPAN distribution.

Report information
The Basics
Id: 78848
Status: resolved
Priority: 0/
Queue: Crypt-SSLeay

People
Owner: nanis [...] runu.moc.invalid
Requestors: nanis [...] runu.moc.invalid
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.64
Fixed in: 0.72



Subject: Allow CPATH and LIBRARY_PATH to be specificed on the command line
Add two command line options --include and --library to point to specific header file and library locations. -- Sinan
This is really bad. It used to be trivially easy to build Crypt::SSLeay against a custom OpenSSL install location. This is now completely broken.
On Fri Jan 18 16:44:01 2013, MISHIKAL wrote: Show quoted text
> This is really bad. It used to be trivially easy to build Crypt::SSLeay > against a custom OpenSSL install location. This is now completely broken.
What this needs, is to add the INC variable, just like Crypt::OpenSSL::Random does, so that the path to the OpenSSL headers can be specified. I can work around the library portion by setting LIBS to point to my libraries. However, there is no corresponding INC variable to set where to find the headers.
On Tue Jan 22 15:54:33 2013, MISHIKAL wrote: Show quoted text
> What this needs, is to add the INC variable, just like > Crypt::OpenSSL::Random does, so that the path to the OpenSSL headers can > be specified. I can work around the library portion by setting LIBS to > point to my libraries. However, there is no corresponding INC variable > to set where to find the headers.
--- Crypt-SSLeay-0.64/Makefile.PL.orig 2013-01-22 12:55:32.000000000 -0800 +++ Crypt-SSLeay-0.64/Makefile.PL 2013-01-22 12:55:54.000000000 -0800 @@ -40,6 +40,8 @@ LIBS => [q{-lz -lssl -lcrypto -lssl32 -lssleay32 -leay32}], + 'INC' => '', # e.g., '-I/usr/include/other' + ($opt_static ? (LINK_TYPE => 'static') : ()), BUILD_REQUIRES => {
On Tue Jan 22 15:56:57 2013, MISHIKAL wrote: Show quoted text
> On Tue Jan 22 15:54:33 2013, MISHIKAL wrote:
> > What this needs, is to add the INC variable, just like > > Crypt::OpenSSL::Random does, so that the path to the OpenSSL headers can > > be specified. I can work around the library portion by setting LIBS to > > point to my libraries. However, there is no corresponding INC variable > > to set where to find the headers.
> > --- Crypt-SSLeay-0.64/Makefile.PL.orig 2013-01-22 12:55:32.000000000
-0800 Show quoted text
> +++ Crypt-SSLeay-0.64/Makefile.PL 2013-01-22 12:55:54.000000000
-0800 Show quoted text
> @@ -40,6 +40,8 @@ > > LIBS => [q{-lz -lssl -lcrypto -lssl32 -lssleay32 -leay32}], > > + 'INC' => '', # e.g., '-I/usr/include/other' > + > ($opt_static ? (LINK_TYPE => 'static') : ()), > > BUILD_REQUIRES => { > >
With the above patch, I can once again link against a custom openssl installation.
To build with my custom openssl installation, I had to set the INC environment variable, to fix the -L directives in the Makefile (from non-existing /usr/local/lib on my box), and to add -lssl -lcrypto to EXTRALIBS and LDLOADLIBS. The config spec did not find them from my $LD_LIBRARY_PATH, and reported them as missing. Thanks
Hello: Thank you for your report. I recently uploaded 0.65_08 to CPAN and it should now handle custom locations better. Once this goes through CPAN testers, I am going to update the documentation and upload 0.66. Best, -- Sinan On Tue Apr 09 08:21:43 2013, MGI wrote: Show quoted text
> To build with my custom openssl installation, I had to set the INC > environment variable, to fix the -L directives in the Makefile (from > non-existing /usr/local/lib on my box), and to add -lssl -lcrypto to > EXTRALIBS and LDLOADLIBS. > The config spec did not find them from my $LD_LIBRARY_PATH, and > reported them as missing. > Thanks