From: erik@dd.nec.com.au (Erik Christiansen)
To: linuxppc-embedded@ozlabs.org
Subject: Re: ARCH=ppc or ARCH=powerpc
Date: Thu, 28 Jun 2007 18:36:24 +1000 [thread overview]
Message-ID: <20070628083624.GE8794@dd.nec.com.au> (raw)
In-Reply-To: <20070628074430.GC8794@dd.nec.com.au>
On Thu, Jun 28, 2007 at 05:44:30PM +1000, Erik Christiansen wrote:
> Encountering a kernel build error with ARCH=ppc, after configuring as much as
> possible for MPC8248, I've just tried ARCH=powerpc on linux-2.6.21.5, with this
> slightly scary result:
Oh dear. Please excuse the noise. That was clearly acute lack of
familiarity with menuconfig. <blush>
Minus fingerfumbling, ARCH=powerpc starts to build, before coughing up a
bunch of compiler errors:
cpm2_common.c:63: error: 'CPM_MAP_ADDR' undeclared
Is that due to this patch not being accepted?:
http://patchwork.ozlabs.org/linuxppc/patch?id=8891
If the patch's "State Superseded" means something else fixes the build
failure, then how could I lay my grubby paws on that little gem?
Erik
next prev parent reply other threads:[~2007-06-28 8:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 21:41 ARCH=ppc or ARCH=powerpc Bizhan Gholikhamseh (bgholikh)
2007-06-28 1:20 ` Kumar Gala
2007-06-28 7:44 ` Erik Christiansen
2007-06-28 8:36 ` Erik Christiansen [this message]
2007-06-29 3:15 ` Kumar Gala
2007-07-01 1:07 ` Josh Boyer
2007-06-28 2:30 ` Bhupender Saharan
-- strict thread matches above, loose matches on Subject: below --
2006-08-24 10:28 Benjamin Delagoutte
2006-08-24 12:38 ` Parav Pandit
2006-08-24 12:49 ` Josh Boyer
2006-08-24 12:58 ` Benjamin Delagoutte
2006-08-24 13:07 ` Josh Boyer
2006-08-24 13:26 ` Matt Porter
2006-08-24 13:23 ` Matt Porter
2006-09-15 23:06 ` Shawn Jin
2006-09-15 23:23 ` Josh Boyer
2007-06-28 1:14 ` Kumar Gala
2006-08-24 12:58 ` Parav Pandit
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=20070628083624.GE8794@dd.nec.com.au \
--to=erik@dd.nec.com.au \
--cc=linuxppc-embedded@ozlabs.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.