From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15678 invoked by alias); 4 Sep 2009 15:16:28 -0000 Received: (qmail 15666 invoked by uid 22791); 4 Sep 2009 15:16:27 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp28.orange.fr (HELO smtp28.orange.fr) (80.12.242.101) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Sep 2009 15:16:22 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2816.orange.fr (SMTP Server) with ESMTP id C87C380000AB; Fri, 4 Sep 2009 17:16:19 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2816.orange.fr (SMTP Server) with ESMTP id B9A3680000B4; Fri, 4 Sep 2009 17:16:19 +0200 (CEST) Received: from r-lnx-leminkainen.bzh.lan (ARennes-252-1-6-178.w83-195.abo.wanadoo.fr [83.195.37.178]) by mwinf2816.orange.fr (SMTP Server) with ESMTP id 92A3680000AB; Fri, 4 Sep 2009 17:16:19 +0200 (CEST) From: "Yann E. MORIN" To: crossgcc@sourceware.org Subject: Re: building patched gcc Date: Fri, 04 Sep 2009 15:16:00 -0000 User-Agent: KMail/1.9.9 Cc: ng@piments.com References: <719dced30909032047j74b8ca79pdb8a9de31ea5ac7@mail.gmail.com> <4AA0D4AF.7010902@piments.com> In-Reply-To: <4AA0D4AF.7010902@piments.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909041716.19266.yann.morin.1998@anciens.enib.fr> X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00006.txt.bz2 Peter, All, On Friday 04 September 2009 10:49:51 ng@piments.com wrote: > I have become aware of the need to patch gcc for certain ARM hardware > and have some patches that need to be applied. If only it was gcc for ARM... A lot of other components require patching for diverse reasons: proper arch support, PR fixes, non-PR fixes... > Is there a convenient way to make sure that the patched source does not > get overwritten by the release tarball when re-running ct-ng? Once crosstool-NG has extracted the tarball, it will not be overwriten but subsequent calls to ct-ng. > If it is necessary to start hacking the build scripts to add the patch > commands , where do I need to be looking ? You don't have to hack the scripts (unless there's a bug, which I am not aware of so far in this part). By default, crosstool-NG comes bundled with a proper set of patches for each version of each supported component. And ct-ng knows where to find this patchset. If you have custom patches, there are two ways you can use them: - as Thomas suggested, include them in the same place crosstool-NG has the existing patches (but you'd better submit them) - or you can have a place on your machine that is completly out of control from crosstool-NG and put your patches there. Then you tell ct-ng where to find those patches, and it will happily get them and apply them. So if you later need to remove the build directory, you don't loose the patches, and on subsequent run, the patches will again be applied. Look at: Paths and misc options ---> [X] Use custom patch directory [ ] Only use custom patches () Custom patch directory Read the help for those two entries, they should be quite self explanatory. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ | | --==< ^_^ >==-- `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | `------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq