On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote:
I just had an idea. Why not use Apple's libssl.so that comes with Leopard Server
Because the goal of the MacPorts project is the contrary of that: we should mess with the sources provided by third parties, not with the binaries distributed by Apple! I have tried to apply the rough workaround I suggested you; these are the simple steps I followed: * extract the sources of Apache with "sudo port extract apache2" * search where in the sources the option "-export-simbol-regex" is defined with: grep -r "-export-symbols-regex" /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_www_apache2 ==> [...] [...] /httpd-2.2.6/configure: test "x$silent" != "xyes" && echo " setting MOD_SSL_LDADD to \"-export-symbols-regex ssl_module\"" [...]/ httpd-2.2.6/configure: MOD_SSL_LDADD="-export-symbols-regex ssl_module" [...] /httpd-2.2.6/configure: apr_addto_bugger="-export-symbols- regex ssl_module" [...] * as suspected, the option is used to build the ssl_module... * let's edit the apache2 Portfile with "sudo port edit apache2" and add our patch to the configure script in the Leopard section: platform darwin 9 { depends_build-append port:gawk post-extract { reinplace "s|-export-symbols-regex ssl_module||g" $ {worksrcpath}/configure } } * after cleaning the apache2 port and compiling it, let's test it: sudo apachectl start * no message errors about missing symbols: we got it! -- Guido