From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Geoff Levand" <geoffrey.levand@am.sony.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Scott Wood" <scottwood@freescale.com>
Subject: BUG: compile failure on ps3-head.S
Date: Thu, 19 Jul 2007 13:49:25 -0600 [thread overview]
Message-ID: <fa686aa40707191249r1e73f6f7s7f2aa4502919e98a@mail.gmail.com> (raw)
commit id bafdb645779c63300763acb383f7b9dd2d427228 (on Linus' tree)
causes breakage on my mpc8349 build (see below). I've worked around
it by removing ps3* from arch/powerpc/boot/Makefile, but I have not
dug into what the 'proper' solution should be.
Cheers,
g.
Toolchain: gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)
Build command: make mpc834x_itxgp_defconfig; make zImage
make ARCH=ppc64 -f scripts/Makefile.build obj=arch/powerpc/boot
arch/powerpc/boot/zImage
ppc_6xx-gcc -m32 -Wp,-MD,arch/powerpc/boot/.ps3-head.o.d
-D__ASSEMBLY__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -Os -msoft-float -pipe -fomit-frame-pointer
-fno-builtin -fPIC -nostdinc -isystem
/home/opt/eldk-4.0/usr/bin/../lib/gcc/powerpc-linux/4.0.0/include
-traditional -nostdinc -c -o arch/powerpc/boot/ps3-head.o
arch/powerpc/boot/ps3-head.S
arch/powerpc/boot/ps3-head.S: Assembler messages:
arch/powerpc/boot/ps3-head.S:40: Error: Unrecognized opcode: `clrldi'
arch/powerpc/boot/ps3-head.S:41: Error: Unrecognized opcode: `mtmsrd'
make[1]: *** [arch/powerpc/boot/ps3-head.o] Error 1
make: *** [zImage] Error 2
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next reply other threads:[~2007-07-19 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 19:49 Grant Likely [this message]
2007-07-19 21:45 ` BUG: compile failure on ps3-head.S Segher Boessenkool
2007-07-19 21:47 ` PS3: Fix build with 32-bit toolchains Geoff Levand
2007-07-19 22:05 ` Kumar Gala
2007-07-19 22:36 ` Geoff Levand
2007-07-19 22:16 ` Grant Likely
2007-07-20 15:31 ` Geoff Levand
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=fa686aa40707191249r1e73f6f7s7f2aa4502919e98a@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=arnd@arndb.de \
--cc=geoffrey.levand@am.sony.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).