From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Stephen
Subject: Build issue with linux next. duplicate member _count in mm_types.h
Date: Wed, 06 Jul 2011 10:55:44 +0100 [thread overview]
Message-ID: <4E143120.2020501@cam.ac.uk> (raw)
Getting:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC arch/arm/kernel/asm-offsets.s
In file included from include/linux/sched.h:64:0,
from arch/arm/kernel/asm-offsets.c:13:
include/linux/mm_types.h:74:15: error: duplicate member '_count'
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
Issue looks to have been introduced by
mm: Rearrange struct page
fc9bb8c768abe7ae10861c3510e01a95f98d5933
Guessing it's a known issue, but just thought I'd flag it up in case
it's something very specific about my build.
gcc-2.6 armv7a
Reverting that patch works, but given I don't know the history, I'm
not proposing doing that in general!
Jonathan
next reply other threads:[~2011-07-06 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 9:55 Jonathan Cameron [this message]
2011-07-06 14:46 ` Build issue with linux next. duplicate member _count in mm_types.h Christoph Lameter
2011-07-07 13:05 ` Piotr Hosowicz
2011-07-07 13:42 ` Christoph Lameter
2011-07-07 13:48 ` Piotr Hosowicz
2011-07-07 14:09 ` Christoph Lameter
2011-07-07 14:41 ` Piotr Hosowicz
2011-07-07 14:54 ` Christoph Lameter
2011-07-07 14:57 ` Jonathan Cameron
2011-07-07 19:07 ` Pekka Enberg
2011-07-07 19:14 ` Christoph Lameter
2011-07-07 19:51 ` Pekka Enberg
2011-07-07 22:56 ` Steven Newbury
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=4E143120.2020501@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).