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>
Subject: Re: Kernel Cross Compiling [update]
Date: Sun, 22 Feb 2004 10:52:09 -0500 [thread overview]
Message-ID: <20040222155209.GA11162@linux-sh.org> (raw)
In-Reply-To: <20040222035350.GB31813@MAIL.13thfloor.at>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Sun, Feb 22, 2004 at 04:53:50AM +0100, Herbert Poetzl wrote:
> linux-2.6.3-rc3 linux-2.6.3
> config build config build
>
> sh/sh: OK FAILED OK FAILED
> sh64/sh: OK FAILED OK FAILED
sh64 doesn't exist in 2.6 yet, attempting to build a kernel for it is futile.
> others seem to require different? binutils (sh and sh64)
>
sh and sh64 require completely different toolchains. They're very different
platforms, and have very little in common.
> linux-2.4.25
> config dep kernel modules
>
> sh/sh: OK OK FAILED FAILED
These are due to erroring on .rept usage for filling in the sys_call_table in
arch/sh/kernel/entry.S, in 2.6 we've already cleaned this up in the LinuxSH
tree by just dropping it and padding out for NR_syscalls, I suppose something
similar will have to be done in the 2.4 case..
> sh64/sh64: OK OK FAILED FAILED
>
The sh64 build errors according to logs[7] are issues with your toolchain,
binutils in particular.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-22 16:32 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 [this message]
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
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=20040222155209.GA11162@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=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