From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Ondrej Jakubcik <ojakubcik@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
Date: Wed, 01 Jul 2015 10:07:00 -0000 [thread overview]
Message-ID: <CAH6eHdTGEc1h7nMOTKAQ5_EpU=z=6jhzxaC0VhLnctgG62mASg@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLuD8cmEzo+NFdAbhCXffeRyfYihWze8HmteDfDkZZbQ6Q@mail.gmail.com>
On 1 July 2015 at 06:28, NightStrike wrote:
> I think the biggest issue is that while the releases of binutils and
> gcc are not in sync, the repository HEAD versions generally are.
Yup, that's my understanding too.
prev parent reply other threads:[~2015-07-01 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 20:50 Ondrej Jakubcik
2015-07-01 1:12 ` Jonathan Wakely
2015-07-01 5:10 ` Ondrej Jakubcik
2015-07-01 5:28 ` NightStrike
2015-07-01 10:07 ` Jonathan Wakely [this message]
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='CAH6eHdTGEc1h7nMOTKAQ5_EpU=z=6jhzxaC0VhLnctgG62mASg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nightstrike@gmail.com \
--cc=ojakubcik@gmail.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).