From owner-freebsd-hackers Wed Aug 4 13:16:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6B28A151AB for ; Wed, 4 Aug 1999 13:16:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA95803; Wed, 4 Aug 1999 14:14:06 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04948; Wed, 4 Aug 1999 14:14:10 -0600 (MDT) Message-Id: <199908042014.OAA04948@harmony.village.org> To: Osokin Sergey Subject: Re: Building a new kernel Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 04 Aug 1999 23:54:46 +0400." References: Date: Wed, 04 Aug 1999 14:14:10 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Osokin Sergey writes: : try to cvsup your source tree to 4.0, then rebuild your system : with simply make world procedure. I can't do that. This system *MUST* be a 3.2-stable system. I was building the kernel to test to see if a nasty NFS bug I've found in -stable is present in the exact same environment but with a -current kernel rather than a -stable one. I was just noting this for people in the future. It is something that I've tradtionally been able to do and I couldn't do it in this case. Others less worldly surely will hit the problem over time... Likely near the time we release 4.0 if the compiler situation remains the same. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message