From: Andrew Dixon <andrew.dixon@seranoa.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: unresolved symbols in kernel (jffs2.o from CVS)
Date: Wed, 17 Apr 2002 10:24:54 -0400 [thread overview]
Message-ID: <3CBD85B6.8EF9E122@seranoa.com> (raw)
Hi Everyone,
I'm trying to compile the latest jffs2 stuff with my 2.4.16 Linux
kernel. I'm trying to keep the jffs2 source separate from Linux (who
wants to track Linux with CVS?) so I'm compiling jffs2 as a modules and
then insmoding jffs2.o. I've symlinked linux/fs/jffs2 to mtd/fs/jffs2
and I've also linked some files from linux/include/linux to
mtd/include/linux. I can now do a:
#make modules
and get a jffs2.o module which I can insmod into my kernel. The problem
is that now I get a list of unresolved kernel symbols:
root@wombat7:~#insmod ./jffs2.o
./jffs2.o: unresolved symbol zlib_inflate
./jffs2.o: unresolved symbol zlib_inflate_workspacesize
./jffs2.o: unresolved symbol zlib_deflate_workspacesize
./jffs2.o: unresolved symbol zlib_inflateInit_
./jffs2.o: unresolved symbol zlib_deflate
./jffs2.o: unresolved symbol zlib_inflateEnd
./jffs2.o: unresolved symbol zlib_deflateInit_
./jffs2.o: unresolved symbol zlib_deflateEnd
root@wombat7:~#grep zlib /proc/ksyms
root@wombat7:~#
I have made a jffs2.o module from the Linux 2.4.16 source and I do not
get these unresolved symbols. Has the zlib stuff moved out of jffs2.o
or something? I think I remember reading something along these lines on
the list.
Anyway, any help that anyone could give me would be greatly appreciated.
Thanks,
Andy
--
Andrew Dixon
Software Engineer
Seranoa Networks
978.897.3434 x231
next reply other threads:[~2002-04-17 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:24 Andrew Dixon [this message]
2002-04-17 14:47 ` unresolved symbols in kernel (jffs2.o from CVS) Chris Wilson
2002-04-17 14:52 ` Tino Keitel
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=3CBD85B6.8EF9E122@seranoa.com \
--to=andrew.dixon@seranoa.com \
--cc=linux-mtd@lists.infradead.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