From: Carl Przybylek <carlp@bioace.net>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 Errors
Date: Tue, 17 Sep 2002 21:18:28 -0400 [thread overview]
Message-ID: <3D87D464.5663351F@bioace.net> (raw)
Seems the patchin.sh file did not link all the kernel files correctly.
When I try to compile 2.4.19 kernel I get a bunch of undefined reference
errors.
I manually linked the jffs2 directory as that was not included. Im
assuming Ive missed some more.
The zlib_inflate_workspacesize is in the lib/zlib_inflate directory do
those directories need to be linked into the kernel source as well?
Any help would be greatly appreciated
Carl Przybylek
fs/fs.o: In function `jffs2_compress':
fs/fs.o(.text+0x3d654): undefined reference to `jffs2_rtime_compress'
fs/fs.o: In function `jffs2_decompress':
fs/fs.o(.text+0x3d6d9): undefined reference to `jffs2_rtime_decompress'
fs/fs.o: In function `jffs2_zlib_compress':
fs/fs.o(.text+0x3e051): undefined reference to `zlib_deflateInit_'
fs/fs.o(.text+0x3e0c1): undefined reference to `zlib_deflate'
fs/fs.o(.text+0x3e0fa): undefined reference to `zlib_deflate'
fs/fs.o(.text+0x3e102): undefined reference to `zlib_deflateEnd'
fs/fs.o(.text+0x3e12e): undefined reference to `zlib_deflateEnd'
fs/fs.o: In function `jffs2_zlib_decompress':
fs/fs.o(.text+0x3e18e): undefined reference to `zlib_inflateInit_'
fs/fs.o(.text+0x3e1e0): undefined reference to `zlib_inflate'
fs/fs.o(.text+0x3e200): undefined reference to `zlib_inflateEnd'
fs/fs.o: In function `jffs2_symlink':
fs/fs.o(.text+0x3e7db): undefined reference to `crc32'
fs/fs.o(.text+0x3e7f9): undefined reference to `crc32'
fs/fs.o(.text+0x3e806): undefined reference to `crc32'
fs/fs.o(.text+0x3e957): undefined reference to `crc32'
fs/fs.o(.text+0x3e99b): undefined reference to `crc32'
fs/fs.o(.text+0x3e9b0): more undefined references to `crc32' follow
fs/fs.o: In function `jffs2_garbage_collect_thread':
fs/fs.o(.text+0x46f50): undefined reference to `set_user_nice'
fs/fs.o: In function `jffs2_flush_wbuf':
fs/fs.o(.text+0x47a37): undefined reference to `crc32'
fs/fs.o: In function `jffs2_zlib_init':
fs/fs.o(.text.init+0xc15): undefined reference to
`zlib_deflate_workspacesize'
fs/fs.o(.text.init+0xc4a): undefined reference to
`zlib_deflate_workspacesize'
fs/fs.o(.text.init+0xc65): undefined reference to
`zlib_inflate_workspacesize'
fs/fs.o(.text.init+0xc9a): undefined reference to
`zlib_inflate_workspacesize'
next reply other threads:[~2002-09-18 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 1:18 Carl Przybylek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 5:35 JFFS2 Errors Shen Aaron-r62966
2004-03-19 8:58 ` David Woodhouse
[not found] <01139FC052A0D411900B00508B9535FC102796E8@ZCH07EXM04.corp.mot.com>
2004-03-19 9:50 ` David Woodhouse
2013-06-13 18:58 Jffs2 errors harsh poshtiwala
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=3D87D464.5663351F@bioace.net \
--to=carlp@bioace.net \
--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 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.