Date: Mon, 8 Nov 1999 22:11:17 +0100 From: Dirk Froemberg <dirk@FreeBSD.org> To: Kris Kennaway <kris@hub.freebsd.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, rse@FreeBSD.org Subject: Re: cvs commit: ports/security/openssl Makefile ports/security/openssl/patches patch-ab ports/security/openssl/pkg PLIST Message-ID: <19991108221117.A59489@physik.TU-Berlin.DE> In-Reply-To: <Pine.BSF.4.10.9911080944460.38503-100000@hub.freebsd.org> References: <199911072219.OAA16209@freefall.freebsd.org> <Pine.BSF.4.10.9911080944460.38503-100000@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kris! On Mon, Nov 08, 1999 at 09:46:32AM -0800, Kris Kennaway wrote: > On Sun, 7 Nov 1999, Dirk Froemberg wrote: > > > dirk 1999/11/07 14:19:50 PST > > > > Modified files: > > security/openssl Makefile > > security/openssl/patches patch-ab > > security/openssl/pkg PLIST > > Log: > > Build and install shared libraries libcrypto.so.1 and libssl.so.1, too. > > Err, is this a good idea? I thought the reason openssl didn't build shared > libraries by default was because the code doesn't work properly in that > case, and this is something they're currently addressing. It would be really bad if the shared libraries don't work properly. Do you know more details? The only thing I found in the mailing list archives is that they are working on shared library support for all major platforms. I could not find any problem reports with shared libraries... I'm sending this to Ralf S. Engelschall, one of the OpenSSL developers, too. Ralf, do you know more about this issue? Regards Dirk -- Dirk Froemberg FreeBSD: The Power to Serve! http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991108221117.A59489>