Re: Unable to install Crypt::SSLeay on Mac OS

[Anonymous Monk]

if you believe you found a bug, you should report it at the appropriate place (after first checking if it has already been reported): https://rt.cpan.org/Public/Dist/Display.html?Name=Crypt-SSLeay

[aixtal]

I am not sure it's a bug. It looks more like some version incompatibilty. (I din't find anything on Cpan nor Google nor superSearch)

[zentara]

Can you get the module source code, and post the results of "perl Makefile.PL"? It sounds like the crypto or ssl libs are not being found, or not linked properly. Look for a message like "libcrypto not found....probably harmless".. :-)

[aixtal]

I am not sure this sheds any light, but as I was poking around with OpenSSL (which I was ready to reinstall), I found a PROBLEM file which says

* System libcrypto.dylib and libssl.dylib are used by system ld on Mac
+OS X.


    NOTE: The problem described here only applies when OpenSSL isn't b
+uilt
    with shared library support (i.e. without the "shared" configurati
+on
    option).  If you build with shared library support, you will have 
+no
    problems as long as you set up DYLD_LIBRARY_PATH properly at all t
+imes.


This is really a misfeature in ld, which seems to look for .dylib libr
+aries
along the whole library path before it bothers looking for .a librarie
+s.  This
means that -L switches won't matter unless OpenSSL is built with share
+d
library support.

The workaround may be to change the following lines in apps/Makefile a
+nd
test/Makefile:

  LIBCRYPTO=-L.. -lcrypto
  LIBSSL=-L.. -lssl

to:

  LIBCRYPTO=../libcrypto.a
  LIBSSL=../libssl.a

It's possible that something similar is needed for shared library supp
+ort
as well.  That hasn't been well tested yet.


Another solution that many seem to recommend is to move the libraries
/usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different
directory, build and install OpenSSL and anything that depends on your
build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to thei
+r
original places.  Note that the version numbers on those two libraries
may differ on your machine.


As long as Apple doesn't fix the problem with ld, this problem buildin
+g
OpenSSL will remain as is. Well, the problem was addressed in 0.9.8f b
+y
passing -Wl,-search_paths_first, but it's unknown if the flag was
supported from the initial MacOS X release.

This is a little opaque to me I admit, but I guess that there is indeed a weird library problem on Mac OS.

[aixtal]

Well actually, it seems to find them. Perl Makefile.PL prompts me for confirmation -- and there is indeed the message "No library found for -lgcc"

Crypt-SSLeay-0.58$ perl Makefile.PL
=======================================================
Only one OpenSSL installation found at /usr
Consider running 'perl Makefile.PL --default' the next
time Crypt::SSLeay is upgraded to select this directory
automatically thereby avoiding the following prompt.
=======================================================
Which SSL install path do you want to use? [/usr] 

BUILD INFORMATION
================================================
ssl library: OpenSSL 0.9.8l in /usr
ssl header:  openssl/ssl.h
libraries:   -L/usr/lib -lssl -lcrypto -lgcc
include dir: -I/usr/include
================================================
Checking if your kit is complete...
Looks good
Note (probably harmless): No library found for -lgcc
Writing Makefile for Crypt::SSLeay
The test suite can attempt to connect to public servers
to ensure that the code is working properly. If you are
behind a strict firewall or have no network connectivity,
these tests may fail (through no fault of the code).
Do you want to run the live tests (y/N)? [N]