From owner-freebsd-stable@FreeBSD.ORG Wed Aug 6 21:55:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B6D71065676 for ; Wed, 6 Aug 2008 21:55:51 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4259F8FC0C; Wed, 6 Aug 2008 21:55:49 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <489A1DE2.1020303@FreeBSD.org> Date: Wed, 06 Aug 2008 23:55:46 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Eugene Kazarinov References: <519867a90808061424t50e14c40t6ab9c6f1d849f53a@mail.gmail.com> In-Reply-To: <519867a90808061424t50e14c40t6ab9c6f1d849f53a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: FreeBSD 6.3/amd64: cvsup: Bus error (core dumped) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2008 21:55:51 -0000 Eugene Kazarinov wrote: > Hello. > Dont know is this list right for this topic, but dont know witch one is. > So > > I got 6.3-STABLE-200807-amd64-disc1.iso > I have installed it > cd /usr/ports/net/cvsup-without-gui/ > make install > make clean > > #cvsup some-stable-sup-file > Connected to cvsup.xxxxxx.ru > Bus error (core dumped) > > I cant get fresh src and ports trees and cant compile fresh 6.X-stable > system with athlon64 optimization. :( > > > How to fix cvsup? > How to keep src-tree of 6.x-stable up-to-date without working cvsup? > How to keep ports-tree up-to-date without working cvsup? > > > PS I manage about 10 servers under 6.x-stable and cvsup under 6.3-stable is > very important for me. > Pls help. This problem has been reported a couple of times but it is not clear what change caused it. Someone needs to do a binary search of the kernel source changes to work out when it started, then we can determine how to fix it. Kris