From: David Howells <dhowells@redhat.com>
To: linux-sh@vger.kernel.org
Subject: Re: Has anyone got gcc-4.7.0 to build an SH64 kernel without dying?
Date: Wed, 30 May 2012 13:02:38 +0000 [thread overview]
Message-ID: <20250.1338382958@redhat.com> (raw)
In-Reply-To: <10426.1338312184@redhat.com>
Kaz Kojima <kkojima@rr.iij4u.or.jp> wrote:
> There were 3 patches for sh64-elf gcc build failure on trunk:
>
> http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00208.html
> http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00209.html
> http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00210.html
They seem to fix the problem, thanks!
Oh, and I think these also fix this:
http://gcc.gnu.org/bugzilla/show_bug.cgi?idR971
Am I right in that?
David
next prev parent reply other threads:[~2012-05-30 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 17:23 Has anyone got gcc-4.7.0 to build an SH64 kernel without dying? David Howells
2012-05-29 20:09 ` Oleg Endo
2012-05-30 4:53 ` Kaz Kojima
2012-05-30 13:02 ` David Howells [this message]
2012-05-31 23:13 ` Oleg Endo
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=20250.1338382958@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-sh@vger.kernel.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