LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Compile 6xx specific code only for 6xx machines
Date: Wed, 15 Dec 2004 15:49:26 +0100	[thread overview]
Message-ID: <1103122166.3406.174.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <20041215143518.GC22316@smtp.west.cox.net>

On Wed, 2004-12-15 at 07:35 -0700, Tom Rini wrote:
> On Wed, Dec 15, 2004 at 03:21:43PM +0100, tglx@linutronix.de wrote:
> 
> > The 6xx specific mmu functions in arch/boot/common/util.S break the compile for
> > other platforms. Compile them for 6xx only.
> 
> They, er, do?  Can you please post a log?  And what toolchain are you
> using?  I'd make a quick guess that the binutils folks are being overly
> 'helpful' again, but perhaps I'm just jaded. :)

I'm compiling for 8540 (e500)

  AS      arch/ppc/boot/common/util.o
/home/tglx/work/repos/linux-ebrain/2.6.10-
rc3/arch/ppc/boot/common/util.S: Assembler messages:
/home/tglx/work/repos/linux-ebrain/2.6.10-
rc3/arch/ppc/boot/common/util.S:76: Error: Unrecognized opcode: `mtsrin'
make[3]: *** [arch/ppc/boot/common/util.o] Error 1
make[2]: *** [arch/ppc/boot/common] Error 2
make[1]: *** [zImage] Error 2
make: *** [_all] Error 2

Toolchain is built with crosstool

binutils-2.15
gcc-3.4.2
glibc-2.3.3

tglx

  reply	other threads:[~2004-12-15 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 14:21 [PATCH] Compile 6xx specific code only for 6xx machines tglx
2004-12-15 14:35 ` Tom Rini
2004-12-15 14:49   ` Thomas Gleixner [this message]
2004-12-15 15:15     ` Kumar Gala
2004-12-15 15:18       ` Thomas Gleixner

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=1103122166.3406.174.camel@tglx.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=trini@kernel.crashing.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