From owner-freebsd-apache@FreeBSD.ORG Tue Apr 8 22:07:24 2014 Return-Path: Delivered-To: apache@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6AA3EC0 for ; Tue, 8 Apr 2014 22:07:24 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16D711AF8 for ; Tue, 8 Apr 2014 22:07:23 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MBrCt-1Wg8dH0I7j-00AkfK; Wed, 09 Apr 2014 00:07:16 +0200 Message-ID: <53447316.6090301@gmx.de> Date: Wed, 09 Apr 2014 00:07:18 +0200 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: apache@FreeBSD.org Subject: Re: www/apache22 not honoring WITH_OPENSSL_PORT=yes under FreeBSD 10? References: <53446581.7070802@gmx.de> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:k5ugOnxNuCR/ZknjUlvlv8RYYJY16YuR+XUvVVYh31k+FE4IqUG 2wVRA2O3dqau2koTq+8PGcYz0VeMOH6BN0Azhcc7BYLb+HpHWEFicylE2nz4/wrL+k9sM7v ZhC2lvjID8OGGXYGP5x9s2xX1C8M2mEYMAzTpG9eMMElbl1aXsjipC0rshQ5IKttfBjuCIe km0bl+l+rxJJIX7YdwKyg== Cc: Philip Jocks X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2014 22:07:24 -0000 On 2014-04-08 23:55, Philip Jocks wrote: > > Am 08.04.2014 um 23:09 schrieb olli hauer : > >> On 2014-04-08 17:58, Philip Jocks wrote: >>> Hej, >>> >>> I just came across this: When building in a fresh jail, mod_ssl.so is linked against the base libraries instead of those from ports: >>> >>> # ldd /var/ports/basejail/usr/ports/www/apache22/work/httpd-2.2.27/modules/ssl/.libs/mod_ssl.so >>> /var/ports/basejail/usr/ports/www/apache22/work/httpd-2.2.27/modules/ssl/.libs/mod_ssl.so: >>> libssl.so.7 => /usr/lib/libssl.so.7 (0x801630000) >>> libcrypto.so.7 => /lib/libcrypto.so.7 (0x801899000) >>> libcrypt.so.5 => /lib/libcrypt.so.5 (0x801c84000) >>> libthr.so.3 => /lib/libthr.so.3 (0x801ea4000) >>> libc.so.7 => /lib/libc.so.7 (0x80081d000) >>> >>> In an older FreeBSD 8.x jail it works as expected. A friend of mine confirmed with a fresh FreeBSD 10 VM. >>> Am I missing something? >>> >> >> Hi Philip, > > Hi Olli, > > thanks for getting back to me. > >> have you also build devel/apr1 with 'WITH_OPENSSL_PORT=yes' in /etc/make.conf? > > Yes, it's a fresh FreeBSD 10.0 jail and my friend tested with a fresh VM with same results. > >> Here are some outputs from apu-1-config, build with OpenSSL from base / ports >> so you can compare it with the output from apr-1-config on your system. >> >> >> OpenSSL base: >> ================= >> $> usr/local/bin/apu-1-config --includes >> -I/usr/local/include/apr-1 -I/usr/include -I/usr/local/include -I/usr/local/include/db5 >> >> /usr/local/bin/apu-1-config --ldflags >> -L/usr/lib -L/usr/local/lib -L/usr/local/lib/db5 >> >> >> OpenSSL ports: >> ================= >> $> /usr/local/bin/apu-1-config --includes >> -I/usr/local/include/apr-1 -I/usr/local/include -I/usr/local/include/db5 >> >> $> /usr/local/bin/apu-1-config --ldflags >> -L/usr/local/lib -L/usr/local/lib/db5 > > mine also has /usr/include and /usr/lib appended: > > # /usr/local/bin/apu-1-config --includes > -I/usr/local/include/apr-1 -I/usr/local/include -I/usr/local/include/db48 -I/usr/include > > # /usr/local/bin/apu-1-config --ldflags > -L/usr/local/lib -L/usr/local/lib/db48 -L/usr/lib > >> >> >> And also important '/usr/local/share/apr/build-1/apr_rules.mk' >> >> diff -nru base_1.5.0.1.5.3/usr/local/share/apr/build-1/apr_rules.mk ports_1.5.0.1.5.3/usr/local/share/apr/build-1/apr_rules.mk >> --- base_1.5.0.1.5.3/usr/local/share/apr/build-1/apr_rules.mk 2014-04-08 23:00:48.000000000 +0200 >> +++ ports_1.5.0.1.5.3/usr/local/share/apr/build-1/apr_rules.mk 2014-04-08 23:00:46.000000000 +0200 >> @@ -42,8 +42,8 @@ >> # configure adds to them for tests, but we restore them at the end. >> # >> CFLAGS=-O2 -pipe -fno-strict-aliasing >> -CPPFLAGS=-I/usr/include >> -LDFLAGS= -L/usr/lib -Wl,-rpath,/usr/lib:/usr/local/lib >> +CPPFLAGS=-I/usr/local/include -I/usr/local/include >> +LDFLAGS= -L/usr/local/lib -Wl,-rpath,/usr/local/lib -L/usr/local/lib >> LIBS= >> DEFS=-DHAVE_CONFIG_H >> > > here I got: > > CPPFLAGS=-I/usr/local/include > LDFLAGS= -L/usr/local/lib -Wl,-rpath,/usr/local/lib > > Can you make anything out of this? > If you build www/apache22 on a fresh FreeBSD 10 box with "WITH_OPENSSL_PORT=yes", does it link to the port instead of base? > Hi Philip, give me some time, I have to cross check this on a 10 VM can take some time until all required port s are build ... -- olli