Date: Fri, 11 Jul 2014 22:46:52 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: olli hauer <ohauer@gmx.de> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r361294 - in head/www/apache22: . files Message-ID: <07B385FE34FF7F5B442C57FC@atuin.in.mat.cc> In-Reply-To: <53C056BD.7080206@gmx.de> References: <201407082131.s68LVnVj008783@svn.freebsd.org> <8612910DC9EAD4272CAA72D9@atuin.in.mat.cc> <53C04A97.7000409@gmx.de> <3EA3824870AA723765109C1F@atuin.in.mat.cc> <53C056BD.7080206@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
+--On 11 juillet 2014 23:27:25 +0200 olli hauer <ohauer@gmx.de> wrote: | It's a long time ago but I remember such failures because OPENSSLBASE was | not set at configure time to correct path. (I suspect thats also the | reason why some ports have a fix .include Mk/bsd.openssl.mk) Well, I poked around a bit, it seems to be all right: # make -V SSL_CONFIGURE_ON --with-ssl=/usr/local The thing is, bsd.openssl.mk also adds some bits to LDFLAGS, it ends up like this: # make -V LDFLAGS -L/usr/local/lib -Wl,-rpath,/usr/local/lib -pthread Maybe it's somehow wrong, but I don't really know. | Will try to find a solution If you need any testing, just let me know :-) Also, I should point out, it only affects 8 and 9, because 10 already has the same version of OpenSSL in the base system, so it doesn't lack things. -- Mathieu Arnold
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07B385FE34FF7F5B442C57FC>