public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
To: linux-sh@vger.kernel.org
Subject: Re: Build error at v2.6.33 of sh-2.6.git
Date: Thu, 18 Mar 2010 07:51:04 +0000	[thread overview]
Message-ID: <4BA1DB68.9090004@dcl.info.waseda.ac.jp> (raw)
In-Reply-To: <4BA1CB09.8060908@dcl.info.waseda.ac.jp>

On 03/18/10 16:09, Conrad Parker wrote:
 > On 18 March 2010 16:06, Magnus Damm<magnus.damm@gmail.com>  wrote:
 >> Hi Hitoshi-san,
 >>
 >> On Thu, Mar 18, 2010 at 3:41 PM, Hitoshi Mitake
 >> <mitake@dcl.info.waseda.ac.jp>  wrote:
 >>> So I have a question, is there the de fact standard of corss compiler
 >>> building kit for SuperH arch?
 >>> If there is, could you tell me?
 >>
 >> I used to build cross compilers all the time. These days I use the
 >> binary distribution provided by codesourcery.
 >>
 >> http://www.codesourcery.com/sgpp/editions.html
 >>
 >> Not sure about the status of upstream gcc, binutils and gdb. If the
 >> specific version of gcc that you are building with fails, please make
 >> sure to upgrade to the latest version and try again. I've also heard
 >> that debian should build fine on sh4, so I guess they have whatever
 >> patches that are needed.
 >
 > info on the debian packages is here::
 >
 > http://wiki.debian.org/SH4
 >
 > cheers,
 >
 > Conrad.
 >

Thanks for your rapid and kind reply, Magnus, Conrad and Paul!

I'd like to test both of toolchain of codesourcery and debian package.
But I'm using Debian, so if debian package works fine, this will be
great help for me :)

Thanks a lot, folks!
        Hitoshi

  parent reply	other threads:[~2010-03-18  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  6:41 Build error at v2.6.33 of sh-2.6.git Hitoshi Mitake
2010-03-18  7:06 ` Magnus Damm
2010-03-18  7:09 ` Conrad Parker
2010-03-18  7:10 ` Paul Mundt
2010-03-18  7:51 ` Hitoshi Mitake [this message]
2010-03-18  9:28 ` Nobuhiro Iwamatsu
2010-03-19  5:40 ` Hitoshi Mitake

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=4BA1DB68.9090004@dcl.info.waseda.ac.jp \
    --to=mitake@dcl.info.waseda.ac.jp \
    --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