public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: ng@piments.com
Subject: Re: building patched gcc
Date: Fri, 04 Sep 2009 15:16:00 -0000	[thread overview]
Message-ID: <200909041716.19266.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4AA0D4AF.7010902@piments.com>

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

  parent reply	other threads:[~2009-09-04 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04  3:47 ct-ng build fails with 'make[1]: *** [configure-binutils] Error 1' Godmar Back
2009-09-04  8:49 ` building patched gcc ng
2009-09-04 12:54   ` Thomas Petazzoni
2009-09-04 15:16   ` Yann E. MORIN [this message]
2009-09-04 15:07 ` ct-ng build fails with 'make[1]: *** [configure-binutils] Error 1' Yann E. MORIN
2009-09-04 19:03   ` Godmar Back
2009-09-04 22:20     ` Yann E. MORIN
2009-09-05 14:13       ` Godmar Back
2009-09-06 13:06         ` Yann E. MORIN
2009-09-06 13:34           ` Godmar Back
2009-09-06 13:39             ` Yann E. MORIN
2009-09-07 14:04               ` Godmar Back
2009-09-07 16:06                 ` Yann E. MORIN
2009-09-09 13:31                   ` Godmar Back
2009-09-09 19:56                     ` Yann E. MORIN
     [not found]                       ` <719dced30909092215qe1bf9a2i1d7f10f15733e11c@mail.gmail.com>
2009-09-10  5:16                         ` Godmar Back

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200909041716.19266.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=ng@piments.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).