From: Olaf Hering <olh@suse.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: 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
Subject: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c
Date: Thu, 5 Aug 2004 19:39:26 +0200 [thread overview]
Message-ID: <20040805173926.GA14028@suse.de> (raw)
In-Reply-To: <20040805172033.GB555@smtp.west.cox.net>
On Thu, Aug 05, Tom Rini wrote:
> On Thu, Aug 05, 2004 at 07:00:44PM +0200, Olaf Hering wrote:
> > On Thu, Aug 05, Tom Rini wrote:
> >
> > > On Thu, Aug 05, 2004 at 04:12:57PM +0200, Olaf Hering wrote:
> > > > On Fri, Jul 30, Tom Rini wrote:
> > > >
> > > > >
> > > > > +aflags-$(CONFIG_PPC64BRIDGE) += -mppc64bridge
> > > >
> > > > this should be -Wa,-mppc64bridge for some reasons.
> > >
> > > That, er, doesn't make sense. The assembler needs -Wa,?
> >
> > The cmdline was 'gcc .. -mppc64bridge ..'
> > But there is more breakage with g5 32bit, I'm looking at it right now.
>
> Hmm. Was cflags-... done correctly?
I have currently no idea whats going on with the cflags. power3 and g5
fails for me with current binutils and hammer branch.
g5 needs the altivec option, because -maltivec -mppc64bridge will disable
altivec again in as. And arch/ppc/kernel/Makefile adds -mppc64bridge
after the cflags in arch/ppc/Makefile. Maybe the EXTRA_CFLAGS can be
removed from arch/ppc/kernel/Makefile?
plain rc3 with g5 32bit (and power3) .config gives this:
gcc -m32 -Wp,-MD,usr/.initramfs_data.o.d -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -Iarch/ppc -D__ASSEMBLY__ -Iarch/ppc -mppc64bridge -c -o usr/initramfs_data.o usr/initramfs_data.S
cc1: error: invalid option `ppc64bridge'
this comes from aflags-$(CONFIG_PPC64BRIDGE) in arch/ppc/Makefile
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2004-08-05 17:39 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
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 [this message]
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=20040805173926.GA14028@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=kumar.gala@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
--cc=tnt@246tNt.com \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox