From: Stuart Wood <stuart.wood@labxtechnologies.com>
To: buildroot@busybox.net
Subject: [Buildroot] configure: error: zlib.h was not found
Date: Mon, 21 May 2007 09:53:39 -0400 [thread overview]
Message-ID: <003801c79baf$6f87a090$7100a8c0@SDW> (raw)
I can't seem to get rid of this error. It's being generated from the
configure
file for libid3tag-0.15.1b. The host system has the zlib installed, but this
looks like its for the target?
Buildroot is set up as:
Target Architecture (arm)
Target Architecture Variant (arm920t)
Target ABI (OABI)
Toolchain type (Build toolchain)
Toolchain Options
????????Kernel Headers (Linux 2.6.20)
????????uClibc C library Version (uClibc 0.9.29)
????????Binutils Version (2.17)
????????GCC compiler Version (4.1.2)
Package Selection
????????BusyBox Version (1.5.0)
????????Audio Libraries and Applications
????????????????[*] madplay
????????????????[*] mpg123
Any thoughts on what I'm doing wrong? Or is this a bug?
checking for assert.h... yes
checking for unistd.h... (cached) yes
checking zlib.h usability... no
checking zlib.h presence... no
checking for zlib.h... no
SDW no
configure: error: zlib.h was not found
*** You must first install zlib (libz) before you can build this package.
*** If zlib is already installed, you may need to use the CPPFLAGS
*** environment variable to specify its installed location, e.g. -I<dir>.
make: ***
[/home/stuart/ArmLinux/buildroot/build_arm/libid3tag-0.15.1b/.configured]
Error 1
--
Sincerely,
Stuart Wood
Lab X Technologies,LLC
176 Anderson Ave., Suite 302
Rochester, NY 14607
next reply other threads:[~2007-05-21 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:53 Stuart Wood [this message]
2007-05-30 14:06 ` [Buildroot] configure: error: zlib.h was not found Peter Korsgaard
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='003801c79baf$6f87a090$7100a8c0@SDW' \
--to=stuart.wood@labxtechnologies.com \
--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