All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <djiang@mvista.com>
To: linuxppc-dev@ozlabs.org
Subject: 440 ebony patch seems to have broken 85xx build on powerpc.git
Date: Thu, 24 May 2007 10:13:10 -0700	[thread overview]
Message-ID: <4655C7A6.2050606@mvista.com> (raw)

Has anyone been able to build mpc85xx_* from the latest powerpc.git? I have
tried mpc85xx_cds and mpc8560_ads. I pulled a new git tree and attempted to
build and hit the error message below.

Also, if I comment out the two lines in arch/powerpc/boot/Makefile that was
introduced by the 440 Ebony support patch everything is fine.

$(obj)/44x.o: BOOTCFLAGS += -Wa,-mbooke
$(obj)/ebony.o: BOOTCFLAGS += -Wa,-mbooke


make -f
/home/djiang/community/git-repos/tmp/ppc-master/scripts/Makefile.modpost vmlinux
  scripts/mod/modpost   -o
/home/djiang/community/git-repos/tmp/ppc-master/Module.symvers
arch/powerpc/kernel/head_fsl_booke.o  init/built-in.o  usr/built-in.o
arch/powerpc/kernel/built-in.o  arch/powerpc/mm/built-in.o
arch/powerpc/lib/built-in.o  arch/powerpc/sysdev/built-in.o
arch/powerpc/platforms/built-in.o  arch/powerpc/math-emu/built-in.o
kernel/built-in.o  mm/built-in.o  fs/built-in.o  ipc/built-in.o
security/built-in.o  crypto/built-in.o  block/built-in.o  lib/lib.a
lib/built-in.o  drivers/built-in.o  sound/built-in.o  net/built-in.o
WARNING: arch/powerpc/mm/built-in.o(.text+0x10bc): Section mismatch: reference
to .init.text:early_get_page (between 'pte_alloc_one_kernel' and 'steal_context')
rm -f .old_version
make ARCH=ppc64 -f scripts/Makefile.build obj=arch/powerpc/boot
arch/powerpc/boot/uImage
  /opt/montavista/cge/devkit/ppc/85xx/bin/ppc_85xx-gcc -m32
-Wp,-MD,arch/powerpc/boot/.ebony.o.d -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-builtin -nostdinc -isystem
/opt/montavista/cge/devkit/ppc/85xx/bin/../lib/gcc/powerpc-montavista-linux-gnuspe/4.2.0/include
-fPIC -fno-stack-protector -Iarch/powerpc/boot
-I/home/djiang/community/git-repos/tmp/ppc-master/arch/powerpc/boot -Wa,-mbooke
-c -o arch/powerpc/boot/ebony.o arch/powerpc/boot/ebony.c
/home/djiang/tmp/cc2UVyci.s: Assembler messages:
/home/djiang/tmp/cc2UVyci.s:142: Error: Unrecognized opcode: `isel'
make[1]: *** [arch/powerpc/boot/ebony.o] Error 1

-- 

------------------------------------------------------
Dave Jiang
Software Engineer
MontaVista Software, Inc.
http://www.mvista.com
------------------------------------------------------

             reply	other threads:[~2007-05-24 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 17:13 Dave Jiang [this message]
2007-05-24 17:37 ` 440 ebony patch seems to have broken 85xx build on powerpc.git Josh Boyer
2007-05-24 17:43   ` Dave Jiang
2007-05-24 18:02 ` Sergei Shtylyov
2007-05-24 18:09   ` Josh Boyer
2007-05-25  1:27     ` David Gibson
2007-05-24 19:05 ` Segher Boessenkool
2007-05-24 19:39   ` Josh Boyer
2007-05-24 20:18     ` Segher Boessenkool
2007-05-24 20:21     ` Arnd Bergmann
2007-05-24 20:24       ` Josh Boyer
2007-05-24 21:07         ` Mark A. Greer
2007-05-24 21:16         ` Arnd Bergmann
2007-05-24 22:08           ` Segher Boessenkool
2007-05-24 22:03         ` Segher Boessenkool
2007-05-24 22:02       ` Segher Boessenkool
2007-05-25  1:30         ` David Gibson
2007-05-25 14:01           ` Segher Boessenkool
2007-05-24 22:09   ` Segher Boessenkool

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=4655C7A6.2050606@mvista.com \
    --to=djiang@mvista.com \
    --cc=linuxppc-dev@ozlabs.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.