From: Paul Larson <plars@austin.ibm.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Frank Davis <fdavis@si.rr.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.9-ac4: undefined reference pgtable_cache_init
Date: 30 Aug 2001 15:17:36 +0000 [thread overview]
Message-ID: <999184657.9362.32.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <20010830172612.F1149@flint.arm.linux.org.uk>
In-Reply-To: <3B8E6467.1030204@si.rr.com> <20010830172612.F1149@flint.arm.linux.org.uk>
On 30 Aug 2001 17:26:12 +0100, Russell King wrote:
> On Thu, Aug 30, 2001 at 12:05:59PM -0400, Frank Davis wrote:
> > Hello,
> > During make bzImage, I received the following:
> >
> > init/main.o: In function 'start_kernel'
> > init/main.o(.text.init+0x842): undefined reference to 'pgtable_cache_init'
>
> Which architecture are you building for?
I've seen this as well on i386. It crops up when you are using HIGHMEM.
In include/asm-i386/pgtable.h you declare pgtable_cache_init if HIGHMEM
is on, or define it to the empty while loop if not. It really needs to
be calling init_pae_pgd_cache instead though. Try this patch against
2.4.9-ac4. I don't know if changing the name of init_pae_pgd_cache was
the Right Thing (tm) to do, but it worked for me. It's not getting
called anywhere else anyways.
-Paul Larson
diff -urN linux-2.4.9-ac4/arch/i386/mm/init.c linux-new/arch/i386/mm/init.c
--- linux-2.4.9-ac4/arch/i386/mm/init.c Thu Aug 30 14:09:00 2001
+++ linux-new/arch/i386/mm/init.c Thu Aug 30 15:01:12 2001
@@ -583,7 +583,7 @@
struct kmem_cache_s *pae_pgd_cachep;
-void __init init_pae_pgd_cache(void)
+void __init pgtable_cache_init(void)
{
/*
* PAE pgds must be 16-byte aligned:
next prev parent reply other threads:[~2001-08-30 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 16:05 2.4.9-ac4: undefined reference pgtable_cache_init Frank Davis
2001-08-30 16:26 ` Russell King
2001-08-30 15:17 ` Paul Larson [this message]
2001-08-30 22:25 ` Russell King
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=999184657.9362.32.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fdavis@si.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.