Date: Sun, 20 Feb 2000 00:52:49 -0800 (PST) From: Kris Kennaway <kris@FreeBSD.org> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: Victor Salaman <salaman@teknos.com>, freebsd-current@FreeBSD.org Subject: Re: openssl in -current Message-ID: <Pine.BSF.4.21.0002200015070.14465-100000@freefall.freebsd.org> In-Reply-To: <88758.951034390@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Feb 2000, Jordan K. Hubbard wrote: > Well, I guess I'll be less frantic about this when I see the ports > infrastructure working properly with this - having openssh fail > came as a rude shock. :) See Jim Bloom's patch of earlier this evening. > I'm also assuming that if I have openssl installed via the base system > and USA_RESIDENT=YES in /etc/make.conf, going off to make openssh will > cause it to build rsaref on my behalf just like it used to? I'd hate > to have something become manual which was formerly automated. No, because openssl is compiled differently if rsaref is present or not - it's not just a matter of dropping in librsaref.so (we can't always just build the version with RSAref stubs because it references symbols in librsaref and so binaries don't link). What will happen is that you'll get a message pointing you to the handbook which explains how to add the relevant openssl package. When you do this (once) you'll be able to build openssh. Is this clear now? Kris > - Jordan ---- "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 freebsd-current" 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.0002200015070.14465-100000>