From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64: allnoconfig build fails
Date: Sun, 22 Jan 2006 01:42:45 +0000 [thread overview]
Message-ID: <200601220242.46298.ak@suse.de> (raw)
In-Reply-To: <200601210320.05771.len.brown@intel.com>
On Saturday 21 January 2006 22:11, Luck, Tony wrote:
> > Need to wrap huge_zonelist function with CONFIG_HUGETLBFS.
> >
> >
> > Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
>
> Fixes this new problem ... allnoconfig still fails for me
> with lots of:
>
> undefined reference to `vmem_map'
>
> and a few
>
> undefined reference to `ia64_pfn_valid'
>
> but these have been around for a while.
Trying without CONFIG_NUMA but with virtual memory map also doesn't work.
Also some of the other obvious combinations in the mm space are broken.
Found this last time I updated the kernel on my ia64 box.
-Andi
next prev parent reply other threads:[~2006-01-22 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 8:20 ia64: allnoconfig build fails Len Brown
2006-01-21 19:14 ` Chen, Kenneth W
2006-01-21 21:11 ` Luck, Tony
2006-01-22 1:42 ` Andi Kleen [this message]
2006-01-22 13:52 ` Robin Holt
2006-01-23 8:52 ` Andi Kleen
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=200601220242.46298.ak@suse.de \
--to=ak@suse.de \
--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