From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 11:40:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EE1D37B401 for ; Sat, 12 Jul 2003 11:40:01 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B9FC43F3F for ; Sat, 12 Jul 2003 11:40:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfmgp.dialup.mindspring.com ([165.247.218.25] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19bPDs-0005Fs-00; Sat, 12 Jul 2003 11:35:52 -0700 Message-ID: <3F105499.BC7768C0@mindspring.com> Date: Sat, 12 Jul 2003 11:34:01 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kientzle@acm.org References: <20030712165749.GA14599@colocall.net> <3F104A71.7060906@acm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4a49d08b37d3194c5cab99a3ad865b1d293caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org cc: Andrey Elperin Subject: Re: make release of CURRENT on 4.7 box X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2003 18:40:01 -0000 Tim Kientzle wrote: > Andrey Elperin wrote: > > Tell me, please, is it a possible to "make release" of CURRENT on 4.7 box > > at present ? > > > > I see that make release stops with a such messages for a couple of days : > > ===> include > > cd /usr/src/include; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make installincludes > > creating osreldate.h from newvers.sh > > *** Error code 2 > > So I'm not the only one who has been bitten by this. > > Try the following patch. Worked for me. Thank you! Does this damage CURRENT on CURRENT or anything like that? If not, I think this should be committed with haste, before anyone can make changes in that area that break this patch working. -- Terry