From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [ia64:noboot 4/4] mm/page_alloc.c:321:14: error: 'PAGES_PER_SECTION' undeclared; did you mean 'U
Date: Fri, 27 Jul 2018 20:36:42 +0000 [thread overview]
Message-ID: <20180727203641.GA17745@rapoport-lnx> (raw)
In-Reply-To: <201807270703.ixR4vo9j%fengguang.wu@intel.com>
On Fri, Jul 27, 2018 at 07:08:40PM +0000, Luck, Tony wrote:
> >> mm/page_alloc.c:321:14: error: 'PAGES_PER_SECTION' undeclared (first use in this function); did you mean 'USEC_PER_SEC'?
>
> Weird. I unpacked that config file and tried to reproduce ... but got a clean build.
>
> Maybe my build flipped some other options because I'm using an ancient compiler?
> I noticed this difference at the top of the output when I diffed my .config with the
> supplied one:
>
> < CONFIG_GCC_VERSION€100
> ---
> > CONFIG_GCC_VERSION@304
>
> Mike: Did you see anything like this when you did cross builds?
Yep, and I think it's not related to the compiler version. Selecting
NO_BOOTMEM allows enabling the DEFERRED_STRUCT_PAGE_INIT option that in
turn causes compilation of the code that uses PAGES_PER_SECTION. The
definition of PAGES_PER_SECTION, though, depends on SPARSEMEM which is not
enabled in allmconfig for ia64.
I've sent a patch [1] to make DEFERRED_STRUCT_PAGE_INIT depend on
SPARSEMEM, it's landed in the akmp tree.
[1] https://lore.kernel.org/lkml/1530279308-24988-1-git-send-email-rppt@linux.vnet.ibm.com/#t
> -Tony
>
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2018-07-27 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 23:43 [ia64:noboot 4/4] mm/page_alloc.c:321:14: error: 'PAGES_PER_SECTION' undeclared; did you mean 'USEC_ kbuild test robot
2018-07-27 19:08 ` [ia64:noboot 4/4] mm/page_alloc.c:321:14: error: 'PAGES_PER_SECTION' undeclared; did you mean 'U Luck, Tony
2018-07-27 20:36 ` Mike Rapoport [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=20180727203641.GA17745@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=linux-ia64@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