From owner-freebsd-current@FreeBSD.ORG Tue Jun 3 13:07:57 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 5553D37B401; Tue, 3 Jun 2003 13:07:57 -0700 (PDT) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6579843F85; Tue, 3 Jun 2003 13:07:56 -0700 (PDT) (envelope-from ak03@gte.com) Received: from kanpc.gte.com (ak03@localhost [127.0.0.1]) h53K7t3D067564; Tue, 3 Jun 2003 16:07:55 -0400 (EDT) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.9/8.12.9/Submit) id h53K7tsx067563; Tue, 3 Jun 2003 16:07:55 -0400 (EDT) Date: Tue, 3 Jun 2003 16:07:54 -0400 From: Alexander Kabaev To: "Crist J. Clark" Message-Id: <20030603160754.3b4da1c4.ak03@gte.com> In-Reply-To: <20030603195600.GA62620@blossom.cjclark.org> References: <3EDCC41F.9060706@he.iki.fi> <20030603120244.26423a3e.ak03@gte.com> <20030603195600.GA62620@blossom.cjclark.org> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.11claws156 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Petri Helenius cc: crist.clark@attbi.com cc: freebsd-threads@freebsd.org Subject: Re: RELENG_4 to RELENG_5_1 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: Tue, 03 Jun 2003 20:07:57 -0000 On Tue, 3 Jun 2003 12:56:01 -0700 "Crist J. Clark" wrote: > > Hmm, I didn't have any trouble building RELENG_5_1 on RELENG_4, but I > have been getting the same failure originally quoted when building > HEAD on RELENG_4 for several days now. > > I suggest that the original poster double-check that he has RELENG_5_1 > and not HEAD. And I do have buildworld logs. I'll send in a separate > mail. No need that. This is a bug and it needs to be fixed. I am working on this. Thanks for the reports. -- Alexander Kabaev