public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Clean config for hp6xx and Hugetlbpage build errors
Date: Mon, 26 Oct 2009 19:11:43 +0000	[thread overview]
Message-ID: <20091026201143.a0e55726.kristoffer.ericson@gmail.com> (raw)

Greetings,

Starting with a fresh ARCH=sh menuconfig and selecting my various bits and pieces
for hp6xx, I end up with this:

In file included from include/linux/hugetlb.h:275,
                 from arch/sh/mm/hugetlbpage.c:14:
/home/kristoffer/work/kernel/linux-hpc.git/arch/sh/include/asm/hugetlb.h: In function `prepare_hugepage_range':
/home/kristoffer/work/kernel/linux-hpc.git/arch/sh/include/asm/hugetlb.h:20: error: `HPAGE_SHIFT' undeclared (first use in this function)
/home/kristoffer/work/kernel/linux-hpc.git/arch/sh/include/asm/hugetlb.h:20: error: (Each undeclared identifier is reported only once
/home/kristoffer/work/kernel/linux-hpc.git/arch/sh/include/asm/hugetlb.h:20: error: for each function it appears in.)
make[1]: *** [arch/sh/mm/hugetlbpage.o] Fel 1
make: *** [arch/sh/mm] Fel 2

Turning off MMU makes it compile nicely. And to make it abit more funny, then reactivating mmu
works fine ;)

So in order to build from scratch I need to :
1. Build with mmu (fails with hugetlb missing HPAGE_SHIFT).
2. build without mmu (works) and stop after awhile.
3. Build with mmu.

So, why is hugetlb defaulting to y?

/Kristoffer

-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

             reply	other threads:[~2009-10-26 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 19:11 Kristoffer Ericson [this message]
2009-10-26 21:59 ` Clean config for hp6xx and Hugetlbpage build errors Paul Mundt
2009-10-27 12:11 ` Kristoffer Ericson

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=20091026201143.a0e55726.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=linux-sh@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