From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 11:47:14 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 7C4A437B401 for ; Sat, 12 Jul 2003 11:47:14 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F34B043FD7 for ; Sat, 12 Jul 2003 11:47:13 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (ugly.x.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h6CIhDgY021625; Sat, 12 Jul 2003 11:43:13 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3F10576E.3060904@acm.org> Date: Sat, 12 Jul 2003 11:46:06 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry Lambert References: <20030712165749.GA14599@colocall.net> <3F104A71.7060906@acm.org> <3F105499.BC7768C0@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Reply-To: kientzle@acm.org 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:47:14 -0000 Terry Lambert wrote: > 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? Don't know, haven't had a chance to try it. To be honest, I was never able to understand how the previous version was supposed to work, since the newvers.sh script was run with a very odd current directory. Tim Kientzle