All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: sh64 build error - sh, kbuild or binutils problem?
Date: Fri, 04 Jul 2008 03:55:55 +0000	[thread overview]
Message-ID: <20080704035555.GB7247@linux-sh.org> (raw)
In-Reply-To: <8763rng2q0.wl%ysato@users.sourceforge.jp>

On Thu, Jul 03, 2008 at 08:24:52PM -0400, Yoshinori Sato wrote:
> At Thu, 3 Jul 2008 19:03:23 +0900,
> Paul Mundt wrote:
> > 
> > On Wed, Jul 02, 2008 at 09:45:27PM -0400, Yoshinori Sato wrote:
> > > At Sun, 1 Jun 2008 14:30:47 +0900,
> > > Paul Mundt wrote:
> > > > 
> > > > On Sat, May 31, 2008 at 11:22:39PM +0300, Adrian Bunk wrote:
> > > > > Minimal example demonstrating the problem:
> > > > > 
> > > > > $ sh64-linux-ar rcs tmp.o
> > > > > $ sh64-linux-ld -EL -r -o tmp2.o tmp.o
> > > > > $ sh64-linux-ld -EL -r -o out.o tmp2.o 
> > > > > sh64-linux-ld: sh3 architecture of input file `tmp2.o' is incompatible with sh5 output
> > > > > $ 
> > > > > 
> > > > Yes, it's a binutils bug. I've hit this on SH-2A zImage builds too, and
> > > > hacked together a patch for it. I'll see about fixing it up fo sh64 too
> > > > and then posting it to the list.
> > > 
> > > I think ld is strict machine type check.
> > > 
> > > This is workaround.
> > > SH-2A build success.
> > > 
> > This is probably a reasonable workaround until fixed versions of binutils
> > are more readily available. Please re-send this with a Signed-off-by and
> > I'll add it to my queue.
> 
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> 
Applied, thanks.

  parent reply	other threads:[~2008-07-04  3:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  1:45 sh64 build error - sh, kbuild or binutils problem? Yoshinori Sato
2008-07-03 10:03 ` Paul Mundt
2008-07-04  0:24 ` Yoshinori Sato
2008-07-04  3:55 ` Paul Mundt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-31 20:22 Adrian Bunk
2008-05-31 20:22 ` Adrian Bunk
2008-06-01  5:30 ` Paul Mundt
2008-06-01  5:30   ` Paul Mundt
2008-06-01 19:53   ` Adrian Bunk
2008-06-01 19:53     ` Adrian Bunk

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=20080704035555.GB7247@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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.