From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Fw: SH7709 BUG on boot (partially bisected)
Date: Mon, 05 Jan 2009 11:54:45 +0000 [thread overview]
Message-ID: <20090105115445.GA21207@linux-sh.org> (raw)
In-Reply-To: <OF2E8062F8.007117EA-ON80257530.004D178D-80257530.004E3CFB@smsc.com>
On Mon, Jan 05, 2009 at 11:32:49AM +0000, Steve.Glendinning@smsc.com wrote:
> Hi Paul,
>
> > > Can you post your toolchain information? Compiler version is the most
> > > important thing here.
> >
> > I've upgraded to the gcc 4.1.1 rpm (also from rpm.linux-sh.org).
>
> Sorry, that should be rpm.sh-linux.org.
>
> Doh, since Friday Linus's tree #errors on gcc 4.1.{0,1}. Is there a more
> recent version available as a binary, or should I build my own cross
> toolchain (crosstool?)?
>
> Is there a specific gcc version you'd recommend for sh cross compilation?
>
There are a couple binary toolchains at:
http://userweb.kernel.org/~lethal/toolchains/
beyond that, you can find some more links on the wiki.
I generally stick with gcc 4.2.x, although have been doing 4.3.x also
recently. The binutils versions tend not to matter too much, in that they
tend to have very little churn in the sh backend.
next prev parent reply other threads:[~2009-01-05 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 14:13 SH7709 BUG on boot (partially bisected) Steve.Glendinning
2008-12-31 23:29 ` Paul Mundt
2009-01-01 11:43 ` Steve.Glendinning
2009-01-01 12:58 ` Steve.Glendinning
2009-01-05 11:32 ` Fw: " Steve.Glendinning
2009-01-05 11:54 ` Paul Mundt [this message]
2009-01-05 12:48 ` Steve.Glendinning
2009-01-05 22:15 ` Paul Mundt
2009-01-08 18:09 ` Kristoffer Ericson
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=20090105115445.GA21207@linux-sh.org \
--to=lethal@linux-sh.org \
--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