public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: yh@bizmail.com.au
To: Michael Trimarchi <trimarchi@gandalf.sssup.it>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Failed to build mkfs.jffs2
Date: Wed, 18 Oct 2006 20:40:34 +1000	[thread overview]
Message-ID: <453604A2.5030000@bizmail.com.au> (raw)
In-Reply-To: <4533905D.1090103@gandalf.sssup.it>

Hi,

I've just realized you may be talking about to config mtd to enable 
ZLIB, is it correct? If yes, could you please explain how to config MTD, 
I saw Kconfig in fs directory, but I could not find mtd.config file?

Thank you.

Jim

Michael Trimarchi wrote:

> yh@bizmail.com.au wrote:
> 
> 
>>Hi,
>>
>>I am using the version mtd-20050122 for a linux arm system, I can build 
>>mtd under arm-linux-gcc, but failed to build a host tool mkfs.jffs2 by 
>>"make CC=cc" in util directory on FC5. Please see following error 
>>messages. Is there any way to fix it, rather than to change a new version?
>>
>>compr_zlib.c:65: error: ‘z_stream’ has no member named ‘zalloc'
>>compr_zlib.c:66: error: ‘z_stream’ has no member named ‘zfree’
>>
>>Thanks.
>>
>>Jim
>>
>>______________________________________________________
>>Linux MTD discussion mailing list
>>http://lists.infradead.org/mailman/listinfo/linux-mtd/
>>
>> 
>>
> 
> Have you a zlib compiled for your target?
> 
> Regards Michael
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

  reply	other threads:[~2006-10-18 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  0:28 Failed to build mkfs.jffs2 yh
2006-10-16 13:59 ` Michael Trimarchi
2006-10-18 10:40   ` yh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17  5:58 yh

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=453604A2.5030000@bizmail.com.au \
    --to=yh@bizmail.com.au \
    --cc=linux-mtd@lists.infradead.org \
    --cc=trimarchi@gandalf.sssup.it \
    /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