From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: tiger_defconfig build fails for 2.6.12-rc2-mm1
Date: Wed, 06 Apr 2005 23:40:25 +0000 [thread overview]
Message-ID: <20050406164025.5fb29977.akpm@osdl.org> (raw)
In-Reply-To: <20050405165047.A21553@unix-os.sc.intel.com>
Rajesh Shah <rajesh.shah@intel.com> wrote:
>
> On Wed, Apr 06, 2005 at 03:48:38PM -0700, Andrew Morton wrote:
> > Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > Do we know what the problem was with
> > > add-a-clear_pages-function-to-clear-pages-of-higher.patch? Was it a build
> > > error or a compile error?
> >
> > err, s/build/runtime/
>
> 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
Oh, OK. The patch I have doesn't add a clear_pages function to ia64 at
all, so I'm not sure what's supposed to be going on.
It almost looks like we lost great chunks of that patch somewhere along the
line.
Oh well, I'll drop it for now. Christoph, could you please double-check
everything (including the x86 mmx thing) and resend?
next prev parent reply other threads:[~2005-04-06 23:40 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 [this message]
2005-04-06 23:45 ` Christoph Lameter
2005-04-06 23:46 ` Rajesh Shah
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=20050406164025.5fb29977.akpm@osdl.org \
--to=akpm@osdl.org \
--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