From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e35.co.us.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTP id F0D3EDDE22 for ; Fri, 25 May 2007 04:10:13 +1000 (EST) Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l4OIA5PN014360 for ; Thu, 24 May 2007 14:10:05 -0400 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l4OIA5Qw269118 for ; Thu, 24 May 2007 12:10:05 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l4OIA5La028939 for ; Thu, 24 May 2007 12:10:05 -0600 Subject: Re: 440 ebony patch seems to have broken 85xx build on powerpc.git From: Josh Boyer To: Sergei Shtylyov In-Reply-To: <4655D353.6000304@ru.mvista.com> References: <4655C7A6.2050606@mvista.com> <4655D353.6000304@ru.mvista.com> Content-Type: text/plain Date: Thu, 24 May 2007 13:09:00 -0500 Message-Id: <1180030140.3360.24.camel@zod.rchland.ibm.com> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2007-05-24 at 22:02 +0400, Sergei Shtylyov wrote: > Dave Jiang wrote: > > > 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 > > I wonder WTF ebony.c gets built for MPC85xx targets? :-O Because it's part of the bootwrapper and all platform files get built no matter what the actual target is at the moment. We might want to take a look at why we're doing that again. josh