From: Paul Mundt <lethal@linux-sh.org>
To: linux-kernel@vger.kernel.org, Jim Wilson <wilson@specifixinc.com>,
Judith Lebzelter <judith@osdl.org>, Dan Kegel <dank@kegel.com>,
cliff white <cliffw@osdl.org>,
"Timothy D. Witham" <wookie@osdl.org>
Cc: Richard Curnow <richard.curnow@superh.com>
Subject: Re: Kernel Cross Compiling [update]
Date: Sun, 22 Feb 2004 12:23:07 -0500 [thread overview]
Message-ID: <20040222172307.GB11162@linux-sh.org> (raw)
In-Reply-To: <20040222170720.GA24703@MAIL.13thfloor.at>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
On Sun, Feb 22, 2004 at 06:07:20PM +0100, Herbert Poetzl wrote:
> but why does the sh/sh case fail?
>
The sh/sh case failed due to the .rept usage. I'm not entirely sure when
this started to pop up, but it does work again in binutils CVS (or at least
it did the last time I checked it out). For the time being, I've just gotten
rid of it entirely and just padded out with sys_ni_syscall. (Look at your
error log for the exact line).
> okay, binutils and gcc seem to 'know' sh and sh64 as
> architectures, (in my case binutils 2.14.90.0.8, and
> gcc 3.3.2, w/o any patches), what binutils/gcc would
> you suggest for building sh or sh64?
>
A lot of that depends on what you're trying to build for. The sh defconfig
is for SH-3, in which case the default gcc and binutils should work just
fine. For SH-2 and SH-4, there's patch work that needs to be done both
for gcc and binutils.
> 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?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-22 17:23 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 [this message]
2004-02-23 13:28 ` Richard Curnow
2004-02-23 14:41 ` Herbert Poetzl
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=20040222172307.GB11162@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=cliffw@osdl.org \
--cc=dank@kegel.com \
--cc=judith@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.curnow@superh.com \
--cc=wilson@specifixinc.com \
--cc=wookie@osdl.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