From: Robert Urban <urban@unix-beratung.de>
To: buildroot@busybox.net
Subject: [Buildroot] problems configuring libcurl
Date: Tue, 10 Mar 2009 10:36:32 +0100 [thread overview]
Message-ID: <49B634A0.30600@unix-beratung.de> (raw)
In-Reply-To: <87tz61aigp.fsf@macbook.be.48ers.dk>
Hi Peter,
Peter Korsgaard wrote:
>>>>>> "Robert" == Robert Urban <urban@unix-beratung.de> writes:
>
> Robert> Hi Folks,
> Robert> i've enabled libcurl in svn-buildroot, but the configure-run fails with:
>
> Robert> configure: Added
> Robert> /big/home/urban/Build/Buildroot/svn/buildroot/build_i586/staging_dir/usr/lib
> Robert> to LD_LIBRARY_PATH
> Robert> checking for inflateEnd in -lz... grep: error while loading shared
> Robert> libraries: libc.so.0: cannot open shared object file: No such
> Robert> file or directory
>
> Are you building for the same architecture as your host? Are you also
> building grep? It seems like configure somehow picked up the target
> version of grep.
erm, yes and no. The host is i686, target is i586. I'm not building grep
explicitly. It is, however, configured in busybox. I don't think the
configure picked up the target grep. This is the error I get if I try to run
the target grep on the host:
-snip-
project_build_i586/robix/root/bin/grep
bash: project_build_i586/robix/root/bin/grep: /lib/ld-uClibc.so.0: bad ELF
interpreter: No such file or directory
-snip-
> Please post your .config
.config can be found at:
http://www.spielwiese.de/rob/Buildroot/config
cheers,
Rob Urban
next prev parent reply other threads:[~2009-03-10 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:55 [Buildroot] problems configuring libcurl Robert Urban
2009-03-10 8:29 ` Peter Korsgaard
2009-03-10 9:36 ` Robert Urban [this message]
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=49B634A0.30600@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox