linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: building sh-2.6 git kernel with gcc 4.1.1 Sourgery G++ Lite 4.4-45
Date: Fri, 19 Mar 2010 08:08:32 +0000	[thread overview]
Message-ID: <20100319080832.GB10003@linux-sh.org> (raw)
In-Reply-To: <201003190856.31112.fabio.giovagnini@aurion-tech.com>

On Fri, Mar 19, 2010 at 08:56:30AM +0100, Fabio Giovagnini wrote:
> sh-linux-gnu-ld: arch/sh/kernel/module.o: uses instructions which are 
> incompatible with instructions used in previous modules
> sh-linux-gnu-ld: failed to merge target specific data of file 
> arch/sh/kernel/module.o
> make[2]: *** [arch/sh/kernel/built-in.o] Errore 1
> make[1]: *** [arch/sh/kernel] Errore 2
> make[1]: uscita dalla directory ?/home/fgiovagnini/sh7203/sh7203-uclinux-
> arn/sh-2.6?
> 
[snip]

> What cound be my problem?
> 
The problem is precisely what the error says, you are mixing and matching
sh2a and sh4a objects which just isn't going to work. The compiler you
are using only targets sh4a, which will not handle sh2a (evident by the
fact all of the sh2a tuning flags aren't part of your CFLAGS but do show
up in the LDFLAGS).

If you are using sh2a you will need a compiler that will deal with sh2a,
which you will most likely have to build yourself. The FDPIC compiler
from codesourcery isn't quite ready for general consumption yet, and the
few vendors that have binary sh2/sh2a toolchains are so laughably out of
date it's not even worth bothering with.

      reply	other threads:[~2010-03-19  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  7:56 building sh-2.6 git kernel with gcc 4.1.1 Sourgery G++ Lite 4.4-45 Fabio Giovagnini
2010-03-19  8:08 ` Paul Mundt [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=20100319080832.GB10003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).