public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64: allnoconfig build fails
Date: Sun, 22 Jan 2006 13:52:42 +0000	[thread overview]
Message-ID: <20060122135242.GA25709@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <200601210320.05771.len.brown@intel.com>

I think I used git bisect correctly and narrowed it down to
this commit:

1be7d9935b9c7fb9bd5964bfaf3ac543381277db

I would guess it is related to the change in pfn_valid around:

-#ifndef CONFIG_DISCONTIGMEM
+#ifdef CONFIG_FLATMEM
# define pfn_valid(pfn) (((pfn) < max_mapnr) && ia64_pfn_valid(pfn))
# define page_to_pfn(page) ((unsigned long) (page - mem_map))
# define pfn_to_page(pfn) (mem_map + (pfn))
-#else
+#elif defined(CONFIG_DISCONTIGMEM)

Thanks,
Robin Holt

On Sat, Jan 21, 2006 at 01:11:38PM -0800, 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.
> 
> -Tony
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2006-01-22 13:52 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
2006-01-22 13:52 ` Robin Holt [this message]
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=20060122135242.GA25709@lnx-holt.americas.sgi.com \
    --to=holt@sgi.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