From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2911 invoked by alias); 30 Aug 2004 16:19:34 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 2903 invoked from network); 30 Aug 2004 16:19:31 -0000 Received: from unknown (HELO uni.thekramers.net) (66.92.68.235) by sourceware.org with SMTP; 30 Aug 2004 16:19:31 -0000 Received: by uni.thekramers.net (Postfix, from userid 500) id 7563C1C184; Mon, 30 Aug 2004 12:19:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by uni.thekramers.net (Postfix) with ESMTP id 750511CB1C6 for ; Mon, 30 Aug 2004 12:19:31 -0400 (EDT) Date: Mon, 30 Aug 2004 17:04:00 -0000 From: David Kramer To: gcc-help@gcc.gnu.org Subject: Re: how to combine gcc and binutils source into one tree In-Reply-To: <1969.192.168.0.4.1093881872.squirrel@nautilus.tsunami.us> Message-ID: References: <1969.192.168.0.4.1093881872.squirrel@nautilus.tsunami.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-08/txt/msg00278.txt.bz2 On Mon, 30 Aug 2004 steve@millersnet.net wrote: > >they have common directories libiberty,include,texinfo,config, etc.... > >what is the best way to merge them? > > > > > >thanks in advance > >Steven > > I ask this question last week, is this not the right list for this question? I will give it my best shot, but I am acutally new to compiling gcc/binutils myself. Gaining Way Too Much experience in it in the last week or so though. In combining projects like this in general, if those common directories have completely identical contents, then you can pull it off. The way you integrate them is by changing the master Makefile to call the new directories too, and to make sure the install targets for the new directories get called too. If I were a betting man (which I'm not), I would try something devious like: - Untar package A into DIR1 - Untar package B into DIR2 - Copy the unique directories from package B to DIR1 - Copy the main Makefile of package B to $DIR1/Makefile.packageb - cd $DIR1 - Configure and make package A - Make package B using the makefile Makefile.packageb One obstacle I fear is that their configure scripts will need different things. I would be fascinated to hear whether this works or not. Let me know. I would also be interested in hearing why you want to do this though. TO save 20 minutes of compile time? ---------------------------------------------------------------------------- DDDD David Kramer david@thekramers.net http://thekramers.net DK KD DKK D You don't usually hear "hydraulics" and "simplicity" DK KD in the same sentence. DDDD Cathy Rogers, Junkyard Wars