From owner-freebsd-current@FreeBSD.ORG Wed Jul 7 07:03:42 2004 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 EDB3416A4CF for ; Wed, 7 Jul 2004 07:03:42 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C166D43D5C for ; Wed, 7 Jul 2004 07:03:42 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i6773fw6057105; Wed, 7 Jul 2004 00:03:42 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i6773dtD056916; Wed, 7 Jul 2004 00:03:39 -0700 (PDT) (envelope-from obrien) Date: Wed, 7 Jul 2004 00:03:39 -0700 From: "David O'Brien" To: Colin Percival Message-ID: <20040707070339.GD38356@dragon.nuxi.com> References: <20040707031735.GA3540@frontfree.net> <20040707041220.GA35497@troutmask.apl.washington.edu> <6.1.0.6.1.20040706212904.03d4fe00@popserver.sfu.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.0.6.1.20040706212904.03d4fe00@popserver.sfu.ca> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: Rewrite cvsup & portupgrade in C X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 07:03:43 -0000 On Tue, Jul 06, 2004 at 09:30:17PM -0700, Colin Percival wrote: > cvsup isn't the problem. ezm3 is the problem. > > This is one of the unusual cases where it's easier to port > the program to a new language than it is to port the language > to a new platform. :-) It is? Have you tried?? I can see this being an issue for AMD64, since GCC 3.2 didn't have good support for AMD64 -- but GCC 3.2 supported all the rest of our platforms just fine. I truly believe it is simply that no one has been willing to even try to port 'ezm3' to IA-64 and PowerPC. Everyone demands JDP do the porting vs. giving it try on their own [asking JDP for advice along the way]. -- -- David (obrien@FreeBSD.org)