From: Tom Rini <trini@kernel.crashing.org>
To: Giuliano Pochini <pochini@shiny.it>
Cc: kumar.gala@freescale.com, tnt@246tNt.com,
linuxppc-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
olh@suse.de, akpm@osdl.org
Subject: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c
Date: Fri, 30 Jul 2004 14:03:18 -0700 [thread overview]
Message-ID: <20040730210318.GS16468@smtp.west.cox.net> (raw)
In-Reply-To: <20040730224828.0f06e37a.pochini@shiny.it>
On Fri, Jul 30, 2004 at 10:48:28PM +0200, Giuliano Pochini wrote:
[snip]
> gcc 3.3.3 + binutils 2.15 fails quite soon here:
>
> AS arch/ppc/kernel/l2cr.o
> arch/ppc/kernel/l2cr.S: Assembler messages:
> arch/ppc/kernel/l2cr.S:110: Error: Unrecognized opcode: `dssall'
> arch/ppc/kernel/l2cr.S:278: Error: Unrecognized opcode: `dssall'
> arch/ppc/kernel/l2cr.S:387: Error: Unrecognized opcode: `dssall'
> make[1]: *** [arch/ppc/kernel/l2cr.o] Error 1
Can you try with the following?
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
===== arch/ppc/Makefile 1.57 vs edited =====
--- 1.57/arch/ppc/Makefile 2004-07-28 21:58:36 -07:00
+++ edited/arch/ppc/Makefile 2004-07-29 12:21:33 -07:00
@@ -22,7 +22,7 @@
LDFLAGS_vmlinux := -Ttext $(KERNELLOAD) -Bstatic
CPPFLAGS += -Iarch/$(ARCH)
-AFLAGS += -Iarch/$(ARCH)
+aflags-y += -Iarch/$(ARCH)
cflags-y += -Iarch/$(ARCH) -msoft-float -pipe \
-ffixed-r2 -Wno-uninitialized -mmultiple
CPP = $(CC) -E $(CFLAGS)
@@ -33,10 +33,16 @@
cflags-y += -mstring
endif
+aflags-$(CONFIG_4xx) += -m405
cflags-$(CONFIG_4xx) += -Wa,-m405
+aflags-$(CONFIG_6xx) += -maltivec
+cflags-$(CONFIG_6xx) += -Wa,-maltivec
+aflags-$(CONFIG_E500) += -me500
cflags-$(CONFIG_E500) += -Wa,-me500
+aflags-$(CONFIG_PPC64BRIDGE) += -mppc64bridge
cflags-$(CONFIG_PPC64BRIDGE) += -Wa,-mppc64bridge
+AFLAGS += $(aflags-y)
CFLAGS += $(cflags-y)
head-y := arch/ppc/kernel/head.o
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-07-30 21:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 15:46 [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 check Tom Rini
2004-07-28 22:00 ` Andrew Morton
2004-07-28 22:07 ` Tom Rini
2004-07-28 22:51 ` Andrew Morton
2004-07-29 15:04 ` Sylvain Munaut
2004-07-29 8:05 ` [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c Giuliano Pochini
2004-07-29 14:43 ` Tom Rini
2004-07-30 18:59 ` Giuliano Pochini
2004-07-30 19:07 ` Tom Rini
2004-07-30 20:48 ` Giuliano Pochini
2004-07-30 21:03 ` Tom Rini [this message]
2004-08-04 10:22 ` Wolfram Quester
2004-08-04 10:41 ` Guido Guenther
2004-08-04 12:37 ` Guido Guenther
2004-08-05 14:12 ` Olaf Hering
2004-08-05 16:54 ` Tom Rini
2004-08-05 17:00 ` Olaf Hering
2004-08-05 17:20 ` Tom Rini
2004-08-05 17:39 ` Olaf Hering
2004-08-05 18:03 ` Tom Rini
2004-08-05 18:00 ` Olaf Hering
2004-08-05 18:14 ` Tom Rini
2004-08-05 19:04 ` Sam Ravnborg
2004-08-05 21:03 ` Matt Porter
2004-08-06 15:32 ` Olaf Hering
[not found] ` <hhacx8hirb.fsf@alsvidh.mathematik.uni-muenchen.de>
2004-08-06 15:38 ` [PATCH] ppc32: Fix building of certain CPU types (Was: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14) Tom Rini
2004-08-02 7:45 ` [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c Olaf Hering
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=20040730210318.GS16468@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=olh@suse.de \
--cc=pochini@shiny.it \
--cc=tnt@246tNt.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