From: Olaf Hering <olh@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc64-dev@ozlabs.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] allow kernel compile with native ppc64 compiler
Date: Mon, 18 Oct 2004 09:54:33 +0200 [thread overview]
Message-ID: <20041018075433.GA24927@suse.de> (raw)
In-Reply-To: <16755.23272.754150.209624@cargo.ozlabs.ibm.com>
On Mon, Oct 18, Paul Mackerras wrote:
> Olaf Hering writes:
>
> > > ... and breaks the compile on older toolchains that don't understand
> > > -m32. We need to make the -m32 conditional on HAS_BIARCH as defined
> > > in arch/ppc64/Makefile.
> >
> > how old?
>
> The gcc that comes with debian sid doesn't understand -m32. That's a
> 32-bit gcc, which means that I set CROSS_COMPILE when doing a ppc64
> kernel compile. With your patch I have to set CROSS32_COMPILE as
> well, which seems silly when I'm compiling on a ppc32 box already.
Makes sense, I confused a native powerpc64-linux gcc from last century
with a native/cross powerpc-linux gcc from last century.
> Ben H suggested making the default BOOTCC be $(CC) -m32, which makes
> sense to me.
That may break cross compile. I will provide a new patch.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2004-10-18 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 18:55 [PATCH] allow kernel compile with native ppc64 compiler Olaf Hering
2004-10-17 21:46 ` Paul Mackerras
2004-10-18 4:56 ` Olaf Hering
2004-10-18 5:55 ` Paul Mackerras
2004-10-18 7:54 ` Olaf Hering [this message]
2004-10-18 10:58 ` Benjamin Herrenschmidt
[not found] <2Qoqo-Ou-41@gated-at.bofh.it>
[not found] ` <2Qr4K-2P8-15@gated-at.bofh.it>
2004-10-18 16:23 ` Andi Kleen
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=20041018075433.GA24927@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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.