Date: Fri, 25 Feb 2000 17:29:02 +0800 From: Peter Wemm <peter@netplex.com.au> To: Kris Kennaway <kris@FreeBSD.org> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/secure/lib Makefile src/secure/lib/libcrypto Makefile Makefile.inc Message-ID: <20000225092902.427131CD7@overcee.netplex.com.au> In-Reply-To: Message from Kris Kennaway <kris@FreeBSD.org> of "Fri, 25 Feb 2000 01:17:23 PST." <Pine.BSF.4.21.0002250111250.48837-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Fri, 25 Feb 2000, Jordan K. Hubbard wrote: > > > > I originally had librsaglue in libcrypto, but it broke a lot of ports > > > which expected to link with it. Now that libdes has been folded into > > > libcrypto, we've broken the other case (everything *has* to link with > > > librsaglue). > > > > I'm not sure I understand. Before there was libcrypto, libdes and > > libRSAglue. > > Before before there was libcrypto and libdes. This broke a lot of ports > which were expecting to link against librsaglue explicitly. > > Then there was libcrypto, libdes and librsaglue. This worked :) > > Then there was libcrypto and librsaglue. This broke things which used to > link only against libdes since now (for US people) they require librsaglue > also. > > Then there was libcrypto. This broke a lot of ports again :-) > > Adding another symlink will probably work, if nothing gets confused by > linking against the same library twice under different names. Where does libRSAglue actually come from? The case where openssl is configured for using RSAREF? Well, things using openssl now don't even have to know. We can totally leave out -lrsaref and -lRSAglue now. I spoke with a few folks about making libRSAglue.a an empty stub file to fix ports that use it. However, if they just left it out (and -lrsaref) it would also work, even though libcrypto uses rsaref internally at runtime. The ports shouldn't even need to know. So that brings me back to the question.. How do ports decide if they are going to use -lrsaref and -lRSAglue? Using ./configure to test if -lcrypto works? USA_RESIDENT? other? Anyway, making a fake libRSAglue.a will fix the ports although it'd be better to fix the problem completely I think. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 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?20000225092902.427131CD7>