Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Feb 2000 10:20:59 -0800 (PST)
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/secure/usr.bin/openssl Makefile src/secure/usr.bin/scp Makefile src/secure/usr.bin/ssh Makefile src/secure/usr.bin/ssh-add Makefile src/secure/usr.bin/ssh-agent Makefile src/secure/usr.bin/ssh-keygen Makefile ... 
Message-ID:  <Pine.BSF.4.21.0002251019240.10630-100000@freefall.freebsd.org>
In-Reply-To: <20000225100408.F41191CE4@overcee.netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Feb 2000, Peter Wemm wrote:

> There aren't two versions from an application's perspective.  It only
> has to use -lcrypto and it's all taken care of.  That's regardless of
> whether it's a US or non-US libcrypto.  The only time that the
> application must make special care is if it's trying to link
> statically.

Yep - the difficulty is getting the right version of the library at the
system level, at sysinstall time.

> With the adjustments I've made, if you supply librsaref, it'll now work
> with -lcrypto -lRSAglue -lrsaref.  It just won't use the last two as
> libRSAglue is a stub for application build compatability and librsaref
> won't be linked against by libcrypto, libcrypto will dlopen() librsaref
> itself.

Excellent, thats what we needed. Thanks.

Kris

----
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson



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?Pine.BSF.4.21.0002251019240.10630-100000>