httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kaspar Brand <httpd-dev.2...@velox.ch>
Subject Re: svn commit: r1428184 - /httpd/httpd/trunk/acinclude.m4
Date Thu, 03 Jan 2013 13:00:22 GMT
On 03.01.2013 12:20, Joe Orton wrote:
>> add --static to pkg-config invocations, so that libraries for
>> static linking are also taken into account (PR 54252 - note that
>> the additional flags will only appear in modules/ssl/modules.mk
>> and ab_LDFLAGS, so potential side effects are limited)
> 
> This is the wrong thing to do in 99% of cases and a static OpenSSL build 
> is the wrong thing to use in 99.99% of cases*, so it seems like a poor 
> default.

Maybe the wording of pkg-config's "--static" option is somewhat
misleading. It doesn't force linking against the static libs (i.e.
lib{ssl,crypto}.a), but outputs the libraries from openssl.pc's
Libs.private line instead.

In most cases, the only relevant difference in the pkg-config
--libs-only-l output when adding "--static" is that "-lz" will appear
there, too, if OpenSSL was configured with "[enable-]zlib". It doesn't
cause anything like "-static", "-Bstatic" or similar to be thrown into
the LDFLAGS mix, i.e. mod_ssl will still be linked against the dynamic
libs if they are found in the search path. (Prior to OpenSSL 1.0.0h and
1.0.1, "--static" doesn't even make any difference in its pkg-config
output, see https://issues.apache.org/bugzilla/show_bug.cgi?id=54252#c2).

Kaspar

Mime
View raw message