From: Steven Newbury <steve@snewbury.org.uk>
To: Christoph Lameter <cl@linux.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Build issue with linux next. duplicate member _count in mm_types.h
Date: Thu, 07 Jul 2011 23:56:46 +0100 [thread overview]
Message-ID: <1310079408.31261.6.camel@infinity> (raw)
In-Reply-To: <alpine.DEB.2.00.1107060933460.17202@router.home>
On Wed, 2011-07-06 at 09:46 -0500, Christoph Lameter wrote:
> On Wed, 6 Jul 2011, Jonathan Cameron wrote:
>
> > 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!
>
> Well _count exists in two unionized structs but always has the same offset
> within the larger struct. Maybe ARM creates different offsets there for
> some reason?
This is due to this fix hitting gcc-4.6:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4784
prev parent reply other threads:[~2011-07-07 23:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 9:55 Build issue with linux next. duplicate member _count in mm_types.h Jonathan Cameron
2011-07-06 9:55 ` Jonathan Cameron
2011-07-06 14:46 ` 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 [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=1310079408.31261.6.camel@infinity \
--to=steve@snewbury.org.uk \
--cc=cl@linux.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@kernel.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.