From: Wink Saville <wink@saville.com>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: Can crosstool-ng build a gcc branch
Date: Tue, 19 Jan 2016 19:46:00 -0000 [thread overview]
Message-ID: <CAKk8isrcjvszNOSyT1hX4BpS-_ekNes_nixhc_YCAFosJMrOBA@mail.gmail.com> (raw)
In-Reply-To: <152589b7890.27f3.dbeb6b5f898efeb98986801052df0b2b@varkonsemi.com>
Bryan, thanks for the help it worked.
For others, here are some pedantic instructions:
* From main menu config page "Crosstool-NG Configuration" select
"Paths and misc options"
* From "Paths and misc options" select "Try features marked as EXPERIMENTAL"
* Press ESC twice quickly to return to main config page
* From main menu config page "Crosstool-NG Configuration" select "C compiler"
* From "C compiler" select "Custom gcc" and two new options will
appear "Full path to custom gcc source" and "Custom GCC Version"
* From "C compiler" select" "Full path to custom gcc source" and add
the path to the <root to gcc> you'd like to build.
You can also select "Custom GCC Version" but that does not change
<root to gcc>/gcc/BASE-VER file as I thought it might,
instead you might want to change it manually. Other files that might
be desirable to change so as to further identify
your build are <root to gcc>/gcc/DATESTAMP and <root to gcc>/gcc/DEV-PHASE.
Note the advice here is from a complete noobie to gcc so take it with
a huge grain of salt.
-- Wink
On Mon, Jan 18, 2016 at 10:39 PM, samy adel <samy.adel@varkonsemi.com> wrote:
> Sorry, actually i don't know what all these messages about.
> Thanks.
>
>
>
> On January 19, 2016 8:21:42 AM Bryan Hundven <bryanhundven@gmail.com> wrote:
>
>> Samy,
>>
>> On Mon, Jan 18, 2016 at 10:13 PM, samy adel <samy.adel@varkonsemi.com>
>> wrote:
>> > Hi,
>> > How can i stop following these emails?
>> > Thanks in advance,
>> > Samy
>>
>> You should open a new message instead of hijacking someone else's message.
>>
>> Searching google for unsubscribing from the list, I found this:
>> https://sourceware.org/lists.html#unsubscribe-simple
>>
>> This list is crossgcc, so send an email to:
>> crossgcc-unsubscribe@sourceware.org
>>
>> Cheers,
>>
>> -Bryan
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2016-01-19 19:46 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
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 [this message]
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=CAKk8isrcjvszNOSyT1hX4BpS-_ekNes_nixhc_YCAFosJMrOBA@mail.gmail.com \
--to=wink@saville.com \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
/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).