linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Michael Neuling <mikey@neuling.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: powerpc allnoconfig
Date: Tue, 03 Mar 2009 13:05:31 -0600	[thread overview]
Message-ID: <1236107131.6800.55.camel@otta> (raw)
In-Reply-To: <20090303085614.07f8aa27.akpm@linux-foundation.org>

On Tue, 2009-03-03 at 08:56 -0800, Andrew Morton wrote:
> On Tue, 3 Mar 2009 11:14:04 +0100 (CET) Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> 
> > > > let us know if that works :-)
> > > 
> > > didn't.  Oh well.
> > 
> > Does allnoconfig work if you force the compiler to be 32-bit, like
> > 
> >     make CC="powerpc64-unknown-linux-gnu-gcc -m32"
> 
> Nope:
> 
> scripts/mod/empty.c:1: error: -m64 requires a PowerPC64 cpu

To build a biarch compiler that defaults to 32-bit, try adding the
option --with-cpu=default32 to your GCC configure options.  You also
shouldn't need --enable-targets=all.  We haven't used that option
for ages when building powerpc64-linux enabled GCCs.

Peter

      reply	other threads:[~2009-03-03 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  1:19 powerpc allnoconfig Andrew Morton
2009-03-03  2:31 ` Michael Neuling
2009-03-03  2:40   ` Andrew Morton
2009-03-03  2:52     ` Stephen Rothwell
2009-03-03  2:55       ` Andrew Morton
2009-03-03  3:19         ` Stephen Rothwell
2009-03-03  4:08           ` Andrew Morton
2009-03-03  4:40             ` Stephen Rothwell
2009-03-03  5:38               ` Andrew Morton
2009-03-03  6:22                 ` Stephen Rothwell
2009-03-03  6:35                   ` Andrew Morton
2009-03-03 10:14             ` Geert Uytterhoeven
2009-03-03 16:56               ` Andrew Morton
2009-03-03 19:05                 ` Peter Bergner [this message]

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=1236107131.6800.55.camel@otta \
    --to=bergner@vnet.ibm.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=akpm@linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=sfr@canb.auug.org.au \
    /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).