From: Robert Urban <urban@unix-beratung.de>
To: buildroot@busybox.net
Subject: [Buildroot] problems configuring libcurl
Date: Tue, 10 Mar 2009 01:55:28 +0100 [thread overview]
Message-ID: <49B5BA80.5090103@unix-beratung.de> (raw)
Hi Folks,
i've enabled libcurl in svn-buildroot, but the configure-run fails with:
-snip-
checking for openssl/engine.h... yes
checking for ENGINE_load_builtin_engines... yes
checking for RAND_status... yes
checking for RAND_screen... no
checking for RAND_egd... yes
checking for CRYPTO_cleanup_all_ex_data... yes
checking for SSL_get_shutdown... yes
checking for yaSSL using OpenSSL compatibility mode... no
configure: Added
/big/home/urban/Build/Buildroot/svn/buildroot/build_i586/staging_dir/usr/lib
to LD_LIBRARY_PATH
checking for inflateEnd in -lz... grep: error while loading shared
libraries: libc.so.0: cannot open shared object file: No such file or directory
no
checking zlib.h usability... grep: error while loading shared libraries:
libc.so.0: cannot open shared object file: No such file or directory
no
checking zlib.h presence... grep: error while loading shared libraries:
libc.so.0: cannot open shared object file: No such file or directory
yes
configure: WARNING: zlib.h: present but cannot be compiled
configure: WARNING: zlib.h: check for missing prerequisite headers?
configure: WARNING: zlib.h: see the Autoconf documentation
configure: WARNING: zlib.h: section "Present But Cannot Be Compiled"
configure: WARNING: zlib.h: proceeding with the preprocessor's result
-snip-
it seems "grep" is failing, but an "ldd" of /bin/grep doesn't even list
"libc.so.0". hmm.
Anyone have a suggestion?
Rob Urban
next reply other threads:[~2009-03-10 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:55 Robert Urban [this message]
2009-03-10 8:29 ` [Buildroot] problems configuring libcurl Peter Korsgaard
2009-03-10 9:36 ` Robert Urban
2009-03-10 11:17 ` Peter Korsgaard
2009-03-10 18:47 ` Robert Urban
2009-03-10 21:03 ` 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=49B5BA80.5090103@unix-beratung.de \
--to=urban@unix-beratung.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.