From: Jan Dittmer <jdi@l4x.org>
To: Paul Mundt <lethal@linux-sh.org>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1
Date: Sun, 22 Jul 2007 13:18:27 +0200 [thread overview]
Message-ID: <46A33D03.3000105@l4x.org> (raw)
In-Reply-To: <20070720151543.GA28274@linux-sh.org>
Paul Mundt wrote:
> On Fri, Jul 20, 2007 at 04:07:21PM +0200, Jan Dittmer wrote:
>> Paul Mundt wrote:
>> Tangential question. Which is the currently recommended cross toolchain
>> for sh64? With "gcc 3.2 20020529", "binutils 020306 20030206" (some
>> binary toolchain from ~2 years ago somewhere off the web) I get [1]
<error snipped>
>> gcc 3.4.x, 4.0.x, 4.1.x don't build for me from source
>> (target -superh-linux-gnu, binutils 2.15.x or 2.17.x).
>
> I've been using sh64-linux targetted toolchains created from the gentoo
> crossdev, which works fine with stock versions. I can send you a tarball
> of the toolchain off-list if you like.
Binutils, gcc versions would be fine to. Meanwhile I got binutils
2.17.50.0.17.20070615 and gcc 4.1.3 20070704 (prerelease) to compile
(supplying it with uclibc- and lk-headers). But compiling 2.6.22-git17
now fails with
CC drivers/video/cfbimgblt.o
CC drivers/video/fb_defio.o
LD drivers/video/built-in.o
LD drivers/built-in.o
sh64-linux-ld: sh3 architecture of input file `drivers/media/built-in.o'
is incompatible with sh5 output
sh64-linux-ld: sh3 architecture of input file `drivers/i2c/built-in.o'
is incompatible with sh5 output
make[2]: *** [drivers/built-in.o] Error 1
make[1]: *** [drivers] Error 2
make: *** [_all] Error 2
Known?
Thanks,
Jan
next prev parent reply other threads:[~2007-07-22 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 9:17 [GIT PULL] Trivial sh64 updates for 2.6.23-rc1 Paul Mundt
2007-07-20 14:07 ` Jan Dittmer
2007-07-20 15:15 ` Paul Mundt
2007-07-22 11:18 ` Jan Dittmer [this message]
2007-07-22 11:42 ` Paul Mundt
2007-07-22 16:39 ` Jan Dittmer
2007-07-22 20:41 ` Paul Mundt
2007-07-23 6:38 ` Jan Dittmer
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=46A33D03.3000105@l4x.org \
--to=jdi@l4x.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@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