[MacPorts] #26137: Apache2 mod_ssl.so pointing to wrong libssl.x.x.x.dylib after ssl upgrade on Tiger

MacPorts noreply at macports.org
Wed Aug 18 06:18:30 PDT 2010


#26137: Apache2 mod_ssl.so pointing to wrong libssl.x.x.x.dylib after ssl upgrade
on Tiger
---------------------------------+------------------------------------------
 Reporter:  dsmithhfx@…          |       Owner:  macports-tickets@…                   
     Type:  defect               |      Status:  new                                  
 Priority:  Normal               |   Milestone:                                       
Component:  ports                |     Version:  1.9.1                                
 Keywords:                       |        Port:                                       
---------------------------------+------------------------------------------
 Hi,

 Yesterday I made a number of new mac ports installations with the goal of
 having a newer version Postfix, and easier way to configure it (according
 to [http://www.macports.info/Postfix this guide]).

 So: new mac ports installations of Postfix and Webmin, with all
 dependencies including SSL. Note the mac ports Postfix and SSL are both
 newer versions than come bundled with Tiger.

 Long story short, the pre-existing Apache2 (also installed via mac ports
 some months ago) mod_ssl.so still points to the old libssl.0.9.8.dylib,
 instead of the newly-installed, libssl.1.0.0.dylib, resulting in the
 following error message when attempting to start Apache2:

 {{{
 httpd: Syntax error on line 98 of /opt/local/apache2/conf/httpd.conf:
 Cannot load /opt/local/apache2/modules/mod_ssl.so into server: Library not
 loaded: /opt/local/lib/libssl.0.9.8.dylib\n  Referenced from:
 /opt/local/apache2/modules/mod_ssl.so\n  Reason: image not found
 }}}

 I was able to start Apache2 after commenting out "LoadModule ssl_module
 modules/mod_ssl.so" in httpd.conf.

 Any chance someone could post the correct mod_ssl.so, as I can't edit and
 recompile(?) the binary file, even though I can open it in a text editor
 and plainly see references to libssl.0.9.8.dylib amongst the binary
 'gibberish' ?

 Or is there a better way to fix this (e.g. re-install Apache 2) ?

 Thanks!

-- 
Ticket URL: <http://trac.macports.org/ticket/26137>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list