From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>
Subject: Re: powerpc allnoconfig
Date: Mon, 2 Mar 2009 21:38:01 -0800 [thread overview]
Message-ID: <20090302213801.1dd255f3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090303154043.fee7902e.sfr@canb.auug.org.au>
On Tue, 3 Mar 2009 15:40:43 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Mon, 2 Mar 2009 20:08:09 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > Right, you have a 64 bit only compiler. Also it is version 4.1.0 which we now black ban (I think).
> >
> > Probably. But I only use it for compilation testing, so the `Your
> > version of gcc miscompiles the __weak directive' thing is a pointless
> > PITA, so I patch it out.
>
> Ah, ok.
>
> > > let us know if that works :-)
> >
> > didn't. Oh well.
>
> Rats!
>
> I think we need a better bug report :-)
> Kernel version?
Current mainline.
> What error do you get now?
Same as before.
> allmodconfig and defconfig turn CONFIG_PPC64 on. allnoconfig turns it
> off so you are trying to build a 32 bit kernel with a 64 bit compiler.
Oh. Well that will tear it.
How does one prepare a powerpc64 allnoconfig?
next prev parent reply other threads:[~2009-03-03 5:38 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 [this message]
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
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=20090302213801.1dd255f3.akpm@linux-foundation.org \
--to=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 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.