From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18793 invoked by alias); 20 Apr 2004 21:23:32 -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 18786 invoked from network); 20 Apr 2004 21:23:32 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 20 Apr 2004 21:23:32 -0000 Received: from drow by nevyn.them.org with local (Exim 4.32 #1 (Debian)) id 1BG2iE-0003K6-Bj; Tue, 20 Apr 2004 17:23:26 -0400 Date: Tue, 20 Apr 2004 22:33:00 -0000 From: Daniel Jacobowitz To: Marcus Rosen Cc: "'gdb@sources.redhat.com'" Subject: Re: compatible versions of gdb6.1 and binutils? Message-ID: <20040420212325.GA12754@nevyn.them.org> Mail-Followup-To: Marcus Rosen , "'gdb@sources.redhat.com'" References: <10EE351D89AE1F488B426AC91EF6EDAB0120C829@server-1.videolocus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10EE351D89AE1F488B426AC91EF6EDAB0120C829@server-1.videolocus.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-04/txt/msg00113.txt.bz2 On Tue, Apr 20, 2004 at 05:21:10PM -0400, Marcus Rosen wrote: > Hey, > > I am working on integrating a simulator for a custom sparc into gdb6.1. > I would like to have the source for gdb and binutils in the same source tree > but from what I can tell there is no evidence of any kind of common tags > across these projects that would indicate how best to merge them. Is there > any kind of common baseline for the shared components (bfd,opcodes,etc) that > I should be aiming for? or is my only option to grab what I can tagged at > the gdb6.1 release and merge in some appropriate binutils directories and > hope to get them to build? > > My motivation is to avoid replication of the shared components and to be > able to easily sync my copies with newer releases should it become > necessary. If you want to do this your best bet will be to take a snapshot from the combined CVS tree rather than using release tarballs. Otherwise, combining them is quite difficult, because all the shared directories evolve. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer