From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 10 22:01:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89F7A16A4CE; Tue, 10 Aug 2004 22:01:59 +0000 (GMT) Received: from lakermmtao11.cox.net (lakermmtao11.cox.net [68.230.240.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCF8143D1D; Tue, 10 Aug 2004 22:01:58 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao11.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP <20040810220157.IFON10626.lakermmtao11.cox.net@dolphin.local.net>; Tue, 10 Aug 2004 18:01:57 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id i7AM1uUq038951; Tue, 10 Aug 2004 17:01:56 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id i7AM1plw038950; Tue, 10 Aug 2004 17:01:51 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040810101020.D88160@carver.gumbysoft.com> Date: Tue, 10 Aug 2004 17:01:51 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Doug White cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: cvsup on amd64 just broke today X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 22:01:59 -0000 On 10-Aug-2004 Doug White wrote: > On Mon, 9 Aug 2004, Conrad J. Sabatier wrote: > >> > Can you run cvsup manually? It appears to be trying to execute a >> > binary as a shell script here. >> >> Tried that, got the same result. >> >> I hadn't noticed it before, but it does strike me as odd that the >> binary package for amd64 would include a file with "i386" in the >> name, and which is, in fact, an ELF 32 binary. Did something >> change today that would effect the handling of such a file, perhaps? > > Possible. In the interim you might try installing this native amd64 > version of cvsup (its a package so pkg_add it): > > http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz > > If that doesn't work for you I can build a package on my amd64 box. Thanks, it works. I'm just wondering, if you're able to build the port under amd64, why isn't it in the ports collection? I'm also wondering if maybe the breakage of the earlier version I had installed may have been related to the recent import of the new "file" command. -- Conrad J. Sabatier -- "In Unix veritas"