All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Meelis Roos <mroos@linux.ee>, paulus@samba.org
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.26-pre5: XFS module link errors on PPC
Date: Wed, 24 Mar 2004 09:17:25 +1100	[thread overview]
Message-ID: <20040323221725.GA733@frodo> (raw)
In-Reply-To: <Pine.GSO.4.44.0403231854160.14177-100000@math.ut.ee>

On Tue, Mar 23, 2004 at 07:20:05PM +0200, Meelis Roos wrote:
> I tried to make enamble a modular XFS on my PPC using current linux-2.4
> bitkeeper snaphot. Unfortunately, there are unresolved symbols in xfs
> module:
> 
> depmod: *** Unresolved symbols in /lib/modules/2.4.26-pre5/kernel/fs/xfs/xfs.o
> depmod:         ioremap_bot
> depmod:         vmalloc_start
> 
> XFS works fine when compiled in statically.
> 

Looks like XFS is picking them up via VMALLOC_START and VMALLOC_END
which are usually constants, but looks like these map to a couple
of global variables on PPC.  This should fix it, but I haven't got
a machine handy to test with...

cheers.

-- 
Nathan


--- arch/ppc/kernel/ppc_ksyms.c.orig	2004-03-24 09:04:15.000000000 +1100
+++ arch/ppc/kernel/ppc_ksyms.c	2004-03-24 09:07:20.000000000 +1100
@@ -161,6 +161,8 @@
 EXPORT_SYMBOL(_outsl_ns);
 EXPORT_SYMBOL(iopa);
 EXPORT_SYMBOL(mm_ptov);
+EXPORT_SYMBOL(vmalloc_start);
+EXPORT_SYMBOL(ioremap_bot);
 EXPORT_SYMBOL(ioremap);
 #ifdef CONFIG_PTE_64BIT
 EXPORT_SYMBOL(ioremap64);

      reply	other threads:[~2004-03-23 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 17:20 2.4.26-pre5: XFS module link errors on PPC Meelis Roos
2004-03-23 22:17 ` Nathan Scott [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=20040323221725.GA733@frodo \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=paulus@samba.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.