public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: olivier.eribon@free.fr
To: linux-mtd@lists.infradead.org
Subject: unresolved symbols in kernel (MTD_CVS and linux 2.4.19pre1)
Date: Tue, 28 May 2002 15:04:45 +0200 (MEST)	[thread overview]
Message-ID: <1022591085.3cf3806d06fc4@imp.free.fr> (raw)

I'm trying to compile the latest MTD_CVS (/home/oeribon/MTD_CVS/mtd) with my
2.4.19pre1 Linux kernel in order to use JFFS2 on Nand flash.
I've symlinked this files in the kernel :

./drivers/mtd                 -> /home/oeribon/MTD_CVS/mtd/drivers/mtd/
./fs/jffs2                    -> /home/oeribon/MTD_CVS/mtd/fs/jffs2/
./fs/ffs2                     -> /home/oeribon/MTD_CVS/mtd/fs/ffs2/
./include/linux/mtd           -> /home/oeribon/MTD_CVS/mtd/include/linux/mtd
./include/linux/jffs.h        -> /home/oeribon/MTD_CVS/mtd/include/linux/jffs.h
./include/linux/jffs2.h       -> /home/oeribon/MTD_CVS/mtd/include/linux/jffs2.h
./include/linux/jffs2_fs_i.h  ->
/home/oeribon/MTD_CVS/mtd/include/linux/jffs2_fs_i.h
./include/linux/zlib.h        -> /home/oeribon/MTD_CVS/mtd/include/linux/zlib.h
./include/linux/zutil.h       -> /home/oeribon/MTD_CVS/mtd/include/linux/zutil.h
./include/linux/zconf.h       -> /home/oeribon/MTD_CVS/mtd/include/linux/zconf.h
./include/linux/jffs2_fs_sb.h ->
/home/oeribon/MTD_CVS/mtd/include/linux/jffs2_fs_sb.h
./include/linux/crc32.h       -> /home/oeribon/MTD_CVS/mtd/fs/jffs2/crc32.h
./kernel/mapped.c             -> /home/oeribon/MTD_CVS/mtd/kernel/mapped.c
./kernel/mixmem.c             -> /home/oeribon/MTD_CVS/mtd/kernel/mixmem.c
./lib/zlib_deflate            -> /home/oeribon/MTD_CVS/mtd/lib/zlib_deflate/
./lib/zlib_inflate            -> /home/oeribon/MTD_CVS/mtd/lib/zlib_inflate/
./util                        -> /home/oeribon/MTD_CVS/mtd/util/

I have the same problem (Andrew Dixon & Chris Wilson (unresolved symbols in
kernel Apr. 2002))

/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:100: undefined reference to
`zlib_deflateInit_'
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:100: relocation truncated to
fit: R_PPC_REL24 zlib_deflateInit_
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:117: undefined reference to
`zlib_deflate'
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:117: relocation truncated to
fit: R_PPC_REL24 zlib_deflate
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:122: undefined reference to
`zlib_deflateEnd'
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:122: relocation truncated to
fit: R_PPC_REL24 zlib_deflateEnd
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:129: undefined reference to
`zlib_deflate'
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:129: relocation truncated to
fit: R_PPC_REL24 zlib_deflate
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:130: undefined reference to
`zlib_deflateEnd'
/home/oeribon/MTD_CVS/mtd/fs/jffs2/compr_zlib.c:130: relocation truncated to
fit: R_PPC_REL24 zlib_deflateEnd

Could you give me some information about tree structure integration of MTD_CVS
and linux kernel.
How can i compile MTD_CVS and a kernel (as 2.4.19) with JFFS2 without any error?

With Regards,
Thanks in advance

Olivier Eribon

                 reply	other threads:[~2002-05-28 13:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1022591085.3cf3806d06fc4@imp.free.fr \
    --to=olivier.eribon@free.fr \
    --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