From: Michael Moser <mmoser@moser-engineering.de>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for jffs2 Filesystem fails with zlib.h not found
Date: Mon, 27 Nov 2006 15:12:28 +0100 [thread overview]
Message-ID: <456AF24C.6050803@moser-engineering.de> (raw)
I try to build a tool chain and initial filesystem for a xscale
prozessor which uses a jffs2 file system. This fails with the following
messages:
> make[1]: Entering directory `/home/michael/development/buildroot/toolchain_build_arm/mtd_orig/util'
> gcc -I../include -O2 -Wall -g -c -o mkfs.jffs2.o mkfs.jffs2.c -g -Wp,-MD,.mkfs.jffs2.c.dep
> mkfs.jffs2.c:68:18: zlib.h: File or Directory not found
> make[1]: *** [mkfs.jffs2.o] Error 1
> make[1]: Leaving directory `/home/michael/development/buildroot/toolchain_build_arm/mtd_orig/util'
> make: *** [/home/michael/development/buildroot/toolchain_build_arm/mtd_orig/util/mkfs.jffs2] Fehler 2
If I try to build the same tool chain for ext2 filesystem it succeeds.
I already tried to change the make file and specifed a path to zlib.h
within the buildroot environment. Then the compilation succeeds but the
linker didn't find a compatible libz
Can anyone give me some hints?
reply other threads:[~2006-11-27 14:12 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=456AF24C.6050803@moser-engineering.de \
--to=mmoser@moser-engineering.de \
--cc=buildroot@busybox.net \
/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.