All of lore.kernel.org
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: tiger_defconfig build fails for 2.6.12-rc2-mm1
Date: Wed, 06 Apr 2005 23:54:21 +0000	[thread overview]
Message-ID: <425476AD.7020109@jp.fujitsu.com> (raw)
In-Reply-To: <20050405165047.A21553@unix-os.sc.intel.com>

Christoph Lameter wrote:
> On Wed, 6 Apr 2005, Rajesh Shah wrote:
> 
> 
>>That was a compile error too:
>>
>>arch/ia64/kernel/ia64_ksyms.c:41: error: `clear_page' undeclared here (not in a function)
>>arch/ia64/kernel/ia64_ksyms.c:41: error: initializer element is not constant
>>arch/ia64/kernel/ia64_ksyms.c:41: error: (near initialization for `__ksymtab_clear_page.value')
>>arch/ia64/kernel/ia64_ksyms.c:41: error: __ksymtab_clear_page causes a section type conflict
>>make[1]: *** [arch/ia64/kernel/ia64_ksyms.o] Error 1
>>
>>After reverting the patch, the resulting kernel booted fine for
>>me.
> 
> 
> Are you sure that the patch was fully applied? The patch adds clear_page
> to include/asm-ia64/page.h and ia64_ksyms does #include <asm/page.h>

There are 2 problems.
1. In arch/ia64/kernel/ia64_ksyms.c clear_page() is EXPORTED.
    But, in  asm-ia64/page.h, clear_page() is just a macro of clear_pages(?,0).
2. In this tree, ia64 has no clear_pages() , I think.
    Only clear_page() exists in ia64/lib/clear_page.S.

Thanks.
-- Kame


      parent reply	other threads:[~2005-04-06 23:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 23:50 tiger_defconfig build fails for 2.6.12-rc2-mm1 Rajesh Shah
2005-04-06  1:50 ` Andrew Morton
2005-04-06  7:51 ` KAMEZAWA Hiroyuki
2005-04-06 16:49 ` Rajesh Shah
2005-04-06 21:56 ` Andrew Morton
2005-04-06 22:36 ` Rajesh Shah
2005-04-06 22:48 ` Andrew Morton
2005-04-06 22:48 ` Andrew Morton
2005-04-06 23:16 ` Rajesh Shah
2005-04-06 23:29 ` Christoph Lameter
2005-04-06 23:40 ` Andrew Morton
2005-04-06 23:45 ` Christoph Lameter
2005-04-06 23:46 ` Rajesh Shah
2005-04-06 23:54 ` KAMEZAWA Hiroyuki [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=425476AD.7020109@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.