From: Tom Rini <trini@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Olaf Hering <olh@suse.de>, Giuliano Pochini <pochini@shiny.it>,
kumar.gala@freescale.com, tnt@246tNt.com,
linuxppc-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
akpm@osdl.org, Jens Schmalzing <j.s@lmu.de>
Subject: [PATCH] ppc32: Fix building of certain CPU types (Was: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14)
Date: Fri, 6 Aug 2004 08:38:01 -0700 [thread overview]
Message-ID: <20040806153801.GE555@smtp.west.cox.net> (raw)
In-Reply-To: <hhacx8hirb.fsf@alsvidh.mathematik.uni-muenchen.de>
On Fri, Aug 06, 2004 at 08:40:08AM +0200, Jens Schmalzing wrote:
> Hi,
>
> Tom Rini writes:
>
> > I mistook AFLAGS for being always invoked with gas, which is not the
> > case. Lets do the following:
>
> > +cpu-as-$(CONFIG_POWER4) += -Wa,-maltivec
> > +cpu-as-$(CONFIG_E500) += -Wa,-me500
> > +cpu-as-$(CONFIG_PPC64BRIDGE) += -Wa,-mppc64bridge
>
> These three lines should be the other way round for a successful build
> on a G5.
Done.
The following corrects how we pass CPU flags to gas. Previous, AFLAGS
was incorrectly assumed to be pased directly to $(AS), which is not the
case.
Concept ack'd by Sam Ravnborg.
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
--- 1.58/arch/ppc/Makefile 2004-07-31 12:16:29 -07:00
+++ edited/arch/ppc/Makefile 2004-08-06 08:35:07 -07:00
@@ -22,28 +22,25 @@
LDFLAGS_vmlinux := -Ttext $(KERNELLOAD) -Bstatic
CPPFLAGS += -Iarch/$(ARCH)
-aflags-y += -Iarch/$(ARCH)
-cflags-y += -Iarch/$(ARCH) -msoft-float -pipe \
+AFLAGS += -Iarch/$(ARCH)
+CFLAGS += -Iarch/$(ARCH) -msoft-float -pipe \
-ffixed-r2 -Wno-uninitialized -mmultiple
CPP = $(CC) -E $(CFLAGS)
CHECK := $(CHECK) -D__powerpc__=1
ifndef CONFIG_E500
-cflags-y += -mstring
+CFLAGS += -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
+cpu-as-$(CONFIG_PPC64BRIDGE) += -Wa,-mppc64bridge
+cpu-as-$(CONFIG_4xx) += -Wa,-m405
+cpu-as-$(CONFIG_6xx) += -Wa,-maltivec
+cpu-as-$(CONFIG_POWER4) += -Wa,-maltivec
+cpu-as-$(CONFIG_E500) += -Wa,-me500
-AFLAGS += $(aflags-y)
-CFLAGS += $(cflags-y)
+AFLAGS += $(cpu-as-y)
+CFLAGS += $(cpu-as-y)
head-y := arch/ppc/kernel/head.o
head-$(CONFIG_8xx) := arch/ppc/kernel/head_8xx.o
--- 1.47/arch/ppc/kernel/Makefile 2004-06-17 23:41:08 -07:00
+++ edited/arch/ppc/kernel/Makefile 2004-08-05 11:10:48 -07:00
@@ -2,16 +2,6 @@
# Makefile for the linux kernel.
#
-ifdef CONFIG_PPC64BRIDGE
-EXTRA_AFLAGS := -Wa,-mppc64bridge
-endif
-ifdef CONFIG_4xx
-EXTRA_AFLAGS := -Wa,-m405
-endif
-ifdef CONFIG_E500
-EXTRA_AFLAGS := -Wa,-me500
-endif
-
extra-$(CONFIG_PPC_STD_MMU) := head.o
extra-$(CONFIG_40x) := head_4xx.o
extra-$(CONFIG_44x) := head_44x.o
--- 1.17/arch/ppc/mm/Makefile 2004-06-17 23:41:08 -07:00
+++ edited/arch/ppc/mm/Makefile 2004-08-02 12:08:32 -07:00
@@ -2,10 +2,6 @@
# Makefile for the linux ppc-specific parts of the memory manager.
#
-ifdef CONFIG_PPC64BRIDGE
-EXTRA_AFLAGS := -Wa,-mppc64bridge
-endif
-
obj-y := fault.o init.o mem_pieces.o \
mmu_context.o pgtable.o
--- 1.33/arch/ppc/platforms/Makefile 2004-07-29 07:39:02 -07:00
+++ edited/arch/ppc/platforms/Makefile 2004-08-05 11:11:06 -07:00
@@ -2,13 +2,6 @@
# Makefile for the linux kernel.
#
-ifdef CONFIG_PPC64BRIDGE
-EXTRA_AFLAGS := -Wa,-mppc64bridge
-endif
-ifdef CONFIG_40x
-EXTRA_AFLAGS := -Wa,-m405
-endif
-
# Extra CFLAGS so we don't have to do relative includes
CFLAGS_pmac_setup.o += -Iarch/$(ARCH)/mm
--- 1.31/arch/ppc/syslib/Makefile 2004-08-02 01:00:42 -07:00
+++ edited/arch/ppc/syslib/Makefile 2004-08-05 11:11:14 -07:00
@@ -2,16 +2,6 @@
# Makefile for the linux kernel.
#
-ifdef CONFIG_PPC64BRIDGE
-EXTRA_AFLAGS := -Wa,-mppc64bridge
-endif
-ifdef CONFIG_4xx
-EXTRA_AFLAGS := -Wa,-m405
-endif
-ifdef CONFIG_E500
-EXTRA_AFLAGS := -Wa,-me500
-endif
-
CFLAGS_prom_init.o += -fPIC
CFLAGS_btext.o += -fPIC
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-08-06 15:46 UTC|newest]
Thread overview: 29+ 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
2004-07-31 12:53 ` Giuliano Pochini
2004-08-02 15:43 ` Tom Rini
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 ` Tom Rini [this message]
2004-08-02 7:45 ` 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=20040806153801.GE555@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=j.s@lmu.de \
--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 \
--cc=torvalds@osdl.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.