From: Jan Dittmer <jdi@l4x.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Trivial sh64 updates for 2.6.23-rc1
Date: Mon, 23 Jul 2007 08:38:08 +0200 [thread overview]
Message-ID: <46A44CD0.8020508@l4x.org> (raw)
In-Reply-To: <20070722204110.GA12101@linux-sh.org>
Paul Mundt wrote:
> On Sun, Jul 22, 2007 at 06:39:08PM +0200, Jan Dittmer wrote:
>> Paul Mundt wrote:
>>> It's known that empty objects require explicit tuning for the ABI,
>>> however, this has never been anything that was fatal. If you flip
>>> something on within each of those subsystems, does the error go away?
>> Yes, thanks this fixes it. Would you accept a patch to modify the
>> defconfig so that it builds by default? Would be most useful for
>> my pet project (http://l4x.org/k/). A fixed toolchain would of course
>> also be nice.
>>
> I'll certainly apply patches that help getting it building, so feel free
> to send updates for that. As I also noted, the empty object thing is
> non-fatal with my toolchain, so I'd also appreciate it if you could put
> a tarball of yours up somewhere so this is a bit easier to verify. I
> suspect this is just something we're going to have to change in binutils,
> however.
You can find it here:
http://l4x.org/~jdittmer/sh64-linux-binutils-2.17-gcc-4.1.3pre.tar.bz2
binutils 2.17.50.0.17 (from ftp.kernel.org)
gcc 4.1.3 prerelease (svn, fixes a build bug for sh64)
Jan
prev parent reply other threads:[~2007-07-23 6:38 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
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 [this message]
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=46A44CD0.8020508@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.