From: Bruce Harada <bruce@ask.ne.jp>
To: Kilobug <kilobug@freesurf.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.1-pre5] Unresolved symbols in nfs module
Date: Mon, 3 Dec 2001 01:17:03 +0900 [thread overview]
Message-ID: <20011203011703.13a2ee1a.bruce@ask.ne.jp> (raw)
In-Reply-To: <3C0A4E56.1070409@freesurf.fr>
In-Reply-To: <3C0A4E56.1070409@freesurf.fr>
On Sun, 02 Dec 2001 16:52:54 +0100
Kilobug <kilobug@freesurf.fr> wrote:
> make modules_install:
>
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.1-pre5; fi
> depmod: *** Unresolved symbols in
> /lib/modules/2.5.1-pre5/kernel/fs/nfs/nfs.o
> depmod: seq_escape
> depmod: seq_printf
The following patch is not guaranteed to not eat your entire HD, chew it up
and spit it out, or for that matter to work.
(Original patch from Tommy Reynolds, but if it breaks anything for you, don't
blame him and preferably not me either).
--- ksyms.c_ORIG Mon Dec 3 01:08:46 2001
+++ ksyms.c Mon Dec 3 01:12:30 2001
@@ -46,6 +46,7 @@
#include <linux/tty.h>
#include <linux/in6.h>
#include <linux/completion.h>
+#include <linux/seq_file.h>
#include <asm/checksum.h>
#if defined(CONFIG_PROC_FS)
@@ -553,3 +554,12 @@
EXPORT_SYMBOL(tasklist_lock);
EXPORT_SYMBOL(pidhash);
+
+/* Sequential file systems */
+
+EXPORT_SYMBOL(seq_open);
+EXPORT_SYMBOL(seq_read);
+EXPORT_SYMBOL(seq_lseek);
+EXPORT_SYMBOL(seq_release);
+EXPORT_SYMBOL(seq_escape);
+EXPORT_SYMBOL(seq_printf);
prev parent reply other threads:[~2001-12-02 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 15:52 [2.5.1-pre5] Unresolved symbols in nfs module Kilobug
2001-12-02 16:17 ` Bruce Harada [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=20011203011703.13a2ee1a.bruce@ask.ne.jp \
--to=bruce@ask.ne.jp \
--cc=kilobug@freesurf.fr \
--cc=linux-kernel@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.