public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org, Dan Kegel <dank@kegel.com>,
	Sean McGoogan <sean.mcgoogan@superh.com>
Subject: Re: Kernel Cross Compiling [update]
Date: Mon, 23 Feb 2004 15:41:49 +0100	[thread overview]
Message-ID: <20040223144149.GC4092@MAIL.13thfloor.at> (raw)
In-Reply-To: <20040223132819.GB16667@malvern.uk.w2k.superh.com>

On Mon, Feb 23, 2004 at 01:28:19PM +0000, Richard Curnow wrote:
> * Paul Mundt <lethal@linux-sh.org> [2004-02-23]:
> > > is there a toolchain/binutils which 'know' and 'support'
> > > the '-isa=sh64' option? maybe it was depreciated?
> > > 
> > I don't know of one out in the wild. SuperH has their own toolchains that
> > support this, and is what I currently use. I'm not sure what the status of
> > their patches are in relation to getting merged into current gcc/binutils.
> > Richard (CC'ed) might know though, Richard?
> 
> The last public release we made of the SH-5 tools is available at
> 
>     ftp://ftp.uk.superh.com/pub/SuperH-GNU/Barcelona-20030414

how are they related to the 'mainline' toolchain?

i.e. is this something completely separate, or do
you follow the binutils/gcc updates from time to time?

what would be the binutils/gcc version which is
'closest' to 'your' toolchain? wouldn't it make
sense to get those changes back into the mainline?

> This URL provides further information:
> 
>     http://sourceforge.net/mailarchive/forum.php?thread_id=1984379&forum_id=9482
> 
> The SH-5 tools we're currently using in-house are a few months more
> advanced than those.  (They date from about August 2003.)  We'd be happy
> to package this version up and make it available if people express
> interest in this.

sure I'm interested *expressing interest*

thanks for the info,

TIA,
Herbert

> BTW, if anyone who's using the 2003_04_14 release has found any
> problems, please do let me know and I'll pass the information on to the
> toolchain guys.
> 
> -- 
> Richard \\\ SH-4/SH-5 Core & Debug Architect
> Curnow  \\\         SuperH (UK) Ltd, Bristol
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2004-02-23 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:53 Kernel Cross Compiling [update] Herbert Poetzl
2004-02-22  6:02 ` Dan Kegel
2004-02-22 15:42   ` Herbert Poetzl
2004-02-22  8:43 ` Geert Uytterhoeven
2004-02-22  9:07 ` Russell King
2004-02-22 15:09   ` Herbert Poetzl
2004-02-22 12:45 ` Dr. David Alan Gilbert
2004-02-22 15:22   ` Herbert Poetzl
2004-02-22 15:52 ` Paul Mundt
2004-02-22 17:07   ` Herbert Poetzl
2004-02-22 17:23     ` Paul Mundt
2004-02-23 13:28       ` Richard Curnow
2004-02-23 14:41         ` Herbert Poetzl [this message]
2004-02-26 13:02           ` Richard Curnow
2004-02-23 19:42 ` Jim Wilson
2004-02-23 20:32   ` Herbert Poetzl
2004-02-24  1:49     ` Dan Kegel
2004-02-24  8:53       ` Herbert Poetzl
  -- strict thread matches above, loose matches on Subject: below --
2004-02-22 16:36 Arnd Bergmann

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=20040223144149.GC4092@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=dank@kegel.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.mcgoogan@superh.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