From: David Woodhouse <dwmw2@infradead.org>
To: Murtada Shah <mshah@yottayotta.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd jffs2 on 2.4.18-rmk3: undefined references
Date: Wed, 24 Apr 2002 07:27:54 +0100 [thread overview]
Message-ID: <8726.1019629674@redhat.com> (raw)
In-Reply-To: <3CC61DDF.3050102@yottayotta.com>
mshah@yottayotta.com said:
> I'm getting undefined references to zlib_deflateInit_,
> zlib_inflateInit_ and some other zlib_<> calls.. which seem to reside
> in the lib/zlib_deflate & lib/zlib_inflate directories of mtd. How do
> I copy these to the linux kernel so I can cross-compile 2.4.18-rmk3
> with latest mtd without undefined reference errors?
ftp://ftp.??.kernel.org/pub/linux/kernel/people/dwmw2/shared-zlib/
The 2.4.19-pre1 version ought to work. Obviously the bits which patch the
stable JFFS2 code to work with shared zlib won't work - ignore those and
drop in the new code.
--
dwmw2
prev parent reply other threads:[~2002-04-24 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 2:52 mtd jffs2 on 2.4.18-rmk3: undefined references Murtada Shah
2002-04-24 6:27 ` David Woodhouse [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=8726.1019629674@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mshah@yottayotta.com \
/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