From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1026 invoked by alias); 3 Oct 2004 18:44:30 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1018 invoked from network); 3 Oct 2004 18:44:30 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 3 Oct 2004 18:44:30 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CEBLR-0002ki-VY; Sun, 03 Oct 2004 14:44:30 -0400 Date: Sun, 03 Oct 2004 18:44:00 -0000 From: Daniel Jacobowitz To: Orjan Friberg Cc: gdb@sources.redhat.com Subject: Re: Upcoming target: CRISv32 Message-ID: <20041003184429.GC10453@nevyn.them.org> Mail-Followup-To: Orjan Friberg , gdb@sources.redhat.com References: <41541817.3020102@axis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41541817.3020102@axis.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-10/txt/msg00034.txt.bz2 On Fri, Sep 24, 2004 at 02:50:31PM +0200, Orjan Friberg wrote: > I'm starting to feel pretty confident about my CRISv32 port, and would > like some advice as to how to proceed. The thing is, the CRISv32 > binutils port won't be submitted for another few weeks. Obviously this > means that gdb for CRISv32 won't build. > > On the other hand, submitting it would have its benefits regarding > ongoing deprecation etc, and (more importantly) I assume it will be > easier to get non-architecture specific patches accepted. > > If submitting a non-buildable port is frowned upon, then I'd be happy to > sit on it until the binutils code is in place. Personally, I would prefer that you wait until it is buildable as-is. -- Daniel Jacobowitz