From: Bryan Hundven <bryanhundven@gmail.com>
To: Wink Saville <wink@saville.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: Can crosstool-ng build a gcc branch
Date: Tue, 19 Jan 2016 05:11:00 -0000 [thread overview]
Message-ID: <CAJ+oik3SNjDORgi2iJppnpfd9YWyBE8uwe=z+qLD4rZMNdFNDQ@mail.gmail.com> (raw)
In-Reply-To: <CAKk8isqbdfhZjPAe5w5Vx5TxCWXyuYapmE4+RBKRNeGfKShQWw@mail.gmail.com>
Wink,
On Mon, Jan 18, 2016 at 8:58 PM, Wink Saville <wink@saville.com> wrote:
> I'd like to test a new gcc feature that is in hjl/interrupt/stage1
> (https://github.com/gcc-mirror/gcc/tree/hjl/interrupt/stage1), is
> there a way to configure ct-ng to build a specific branch or make a
> specific sha1?
Sure, just clone down gcc and checkout the stage1 branch.
If you want a specific sha1, just checkout out the specific commit.
Clone down the latest crosstool-ng master. Choose a sample that is
close to the target you want and in menu config, under compiler choose
custom and set the location to the absolute path to where you cloned
down gcc, and set the version to something. Maybe in this case set
version to stage1.
Cheers,
-Bryan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2016-01-19 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 4:59 Wink Saville
2016-01-19 5:11 ` Bryan Hundven [this message]
2016-01-19 5:39 ` Wink Saville
2016-01-19 6:08 ` Wink Saville
2016-01-19 6:13 ` samy adel
2016-01-19 6:21 ` Bryan Hundven
2016-01-19 6:39 ` samy adel
2016-01-19 19:46 ` Wink Saville
2016-01-19 6:22 ` Bryan Hundven
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='CAJ+oik3SNjDORgi2iJppnpfd9YWyBE8uwe=z+qLD4rZMNdFNDQ@mail.gmail.com' \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=wink@saville.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).