From: Pavel Roskin <proski@gnu.org>
To: buildroot@busybox.net
Subject: [Buildroot] Build fails with zlib.h not found
Date: Fri, 01 Dec 2006 03:17:20 -0500 [thread overview]
Message-ID: <1164961040.4870.74.camel@dv> (raw)
In-Reply-To: <456F5CEE.7060405@moser-engineering.de>
On Thu, 2006-11-30 at 23:36 +0100, Michael Moser wrote:
> 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
[skip]
> Can anyone give me some hints?
Since mkfs.jffs2.c is compiled by gcc for the host system, you need the
zlib development package on the host system. It's called zlib-devel on
Fedora and provides both the header and the library. I'm not sure about
other distros, but it's likely a similar name, something matching
{libz,zlib}{,1}-{dev,devel}
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-12-01 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 22:36 [Buildroot] Build fails with zlib.h not found Michael Moser
2006-12-01 8:17 ` Pavel Roskin [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=1164961040.4870.74.camel@dv \
--to=proski@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox