From owner-freebsd-stable Mon Mar 20 12:45:12 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 10CF637C7C4; Mon, 20 Mar 2000 12:21:33 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA90253; Mon, 20 Mar 2000 12:21:33 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 20 Mar 2000 12:21:32 -0800 (PST) From: Kris Kennaway To: Matt Heckaman Cc: FreeBSD-STABLE Subject: Re: Some observations on 4.0-release and 4.0-stable In-Reply-To: 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 Mon, 20 Mar 2000, Matt Heckaman wrote: > First of all, I'd like to say that I'm finding FreeBSD 4.0 quite nice > indeed, some very nice advancements over 3.x. Here are some things I've > noticed so far though; > > * make world bombs if MAKE_KERBEROS4=NO, but I suppose I should be making > that nonetheless, yes? =) The contents of MAKE_KERBEROS[45] don't matter, it only looks whether or not the variable is set. Similarly, doing NOCRYPT=NO won't cause the build to compile with crypto support (two wrongs make a right), it will compile withOUT crypto. I think sheldonh was looking at documenting this better in make.conf. However, world builds with MAKE_KERBEROS4 set _should_ work, if you have up-to-date 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