From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8563 invoked by alias); 5 Jul 2005 09:40:59 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 8554 invoked by uid 22791); 5 Jul 2005 09:40:56 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 05 Jul 2005 09:40:55 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j659esfB015748 for ; Tue, 5 Jul 2005 05:40:54 -0400 Received: from pobox.surrey.redhat.com (pobox.surrey.redhat.com [172.16.10.17]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j659elV25708; Tue, 5 Jul 2005 05:40:48 -0400 Received: from [172.31.0.98] (vpn83-124.boston.redhat.com [172.16.83.124]) by pobox.surrey.redhat.com (8.12.8/8.12.8) with ESMTP id j659eh3N001015; Tue, 5 Jul 2005 10:40:43 +0100 Message-ID: <42CA5681.30808@redhat.com> Date: Tue, 05 Jul 2005 09:40:00 -0000 From: Nick Clifton User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) MIME-Version: 1.0 To: Andrew McCall CC: binutils@sources.redhat.com Subject: Re: Compiling, --target question... References: <4aa50a4605070408496d972ce3@mail.gmail.com> <4aa50a460507041511ee61973@mail.gmail.com> <42CA4D25.8010705@redhat.com> <4aa50a460507050234e00789e@mail.gmail.com> In-Reply-To: <4aa50a460507050234e00789e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00086.txt.bz2 Hi Andrew, > I spent the night hacking around the build system, and I think I > managed to get it to target powerpc-pc-haiku using elf, but I don't > really know how to extract what I have done to make a patch. If I > upload a tar.gz of what I have done, can someone take a look to see if > its right? Well it really is a lot easier for us if you can provide a patch (or set of patches). If you are using the binutils sources checked out of the CVS repository (which is what we would recommend for this kind of work) then all you need to do is run "cvs diff -cp" at the top level of the sources in order to generate a patch file. If you only have a tarball then you can still create a patch by getting hold of another copy of the source tarball (from your backups, you do keep backups, right ? :-) and then running "diff -rcp " at the top level. Cheers Nick