public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org, cl@linux.com
Subject: page->_count build failure [was: mmotm 2011-07-08-12-50 uploaded]
Date: Mon, 11 Jul 2011 22:27:22 +0200	[thread overview]
Message-ID: <4E1B5CAA.7070001@gmail.com> (raw)
In-Reply-To: <201107082028.p68KSWWf013053@imap1.linux-foundation.org>

On 07/08/2011 09:50 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2011-07-08-12-50 has been uploaded to

Hi, am I the only one encountering a build failure due to double
definition of _count in page struct introduced by:
commit fc9bb8c768abe7ae10861c3510e01a95f98d5933
Author: Christoph Lameter <cl@linux.com>
Date:   Wed Jun 1 12:25:48 2011 -0500

    mm: Rearrange struct page

in the -next tree?

$ make
...
  CC      arch/x86/kernel/asm-offsets.s
In file included from include/linux/sched.h:64:0,
                 from arch/x86/kernel/asm-offsets.c:9:
include/linux/mm_types.h:74:15: error: duplicate member ‘_count’
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
$ gcc --version
gcc (SUSE Linux) 4.6.0 20110607 [gcc-4_6-branch revision 174741]

regards,
-- 
js

  parent reply	other threads:[~2011-07-11 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 19:50 mmotm 2011-07-08-12-50 uploaded akpm
2011-07-10 18:44 ` [PATCH -mmotm] misc: fix eeprom printk format Randy Dunlap
2011-07-11 20:27 ` Jiri Slaby [this message]
2011-07-11 20:41   ` page->_count build failure [was: mmotm 2011-07-08-12-50 uploaded] Andrew Morton
2011-07-11 20:45     ` Pekka Enberg
2011-07-11 20:47       ` Jiri Slaby
2011-07-11 20:51         ` Pekka Enberg
2011-07-11 21:00           ` Andrew Morton
2011-07-11 21:04       ` Jiri Slaby

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=4E1B5CAA.7070001@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.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