From: Rajesh Shah <rajesh.shah@intel.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:46:19 +0000 [thread overview]
Message-ID: <20050406164615.B32116@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050405165047.A21553@unix-os.sc.intel.com>
On Wed, Apr 06, 2005 at 04:29:24PM -0700, Christoph Lameter wrote:
> On Wed, 6 Apr 2005, Rajesh Shah wrote:
>
> > 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
> >
>
> 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>
Well, I'd built my -rc2-mm1 tree by applying the -rc2 patch
followed by the -mm1 patch from kernel.org. It applied cleanly
so the problem is probably that the wrong version of your patch
got included in the -mm1 patch.
Rajesh
next prev parent reply other threads:[~2005-04-06 23:46 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 [this message]
2005-04-06 23:54 ` KAMEZAWA Hiroyuki
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=20050406164615.B32116@unix-os.sc.intel.com \
--to=rajesh.shah@intel.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