From owner-freebsd-stable Wed Jun 7 12:20:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B39EE37BFBF; Wed, 7 Jun 2000 12:20:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA22602; Wed, 7 Jun 2000 12:20:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 7 Jun 2000 12:20:40 -0700 (PDT) From: Kris Kennaway To: Eric Ogren Cc: Ben Speirs , =?iso-8859-1?Q?Joachim_Str=F6mbergson?= , FreeBSD-Stable Subject: Re: major problems doing buildworld after cvsup in FreeBSD 4.0 In-Reply-To: <20000607095321.A7737@earthlink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Jun 2000, Eric Ogren wrote: > To both of you; are you *sure* you're sup'ing the crypto sources? In > 4.0-STABLE, you need crypto to build the system (there is a > NOCRYPTO option in /etc/defaults/make.conf which should work, however). No you don't, at least you shouldn't have to. Crypto is *recommended*, but not mandatory. I can't remember if there was breakage in 4.0-RELEASE, but what *will* get you is if you have old crypto sources lying around (or just the directories) because then they will be "autodetected". I recommend either: 1) cvsupping/installing crypto sources as well, that way you get OpenSSH support. 2) trying with an explicit NOCRYPTO=1 to force it not to look for crypto sources. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message