From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] problems configuring libcurl
Date: Tue, 10 Mar 2009 12:17:13 +0100 [thread overview]
Message-ID: <87ljrdaapy.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49B634A0.30600@unix-beratung.de> (Robert Urban's message of "Tue\, 10 Mar 2009 10\:36\:32 +0100")
>>>>> "Robert" == Robert Urban <urban@unix-beratung.de> writes:
Hi,
Robert> bash: project_build_i586/robix/root/bin/grep:
Robert> /lib/ld-uClibc.so.0: bad ELF interpreter: No such file or
Robert> directory -snip-
>> Please post your .config
Robert> .config can be found at:
Robert> http://www.spielwiese.de/rob/Buildroot/config
It builds fine here (on a x86_64 host though). I'll change the target
to x86_64 and try again.
What distribution are you using?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-03-10 11:17 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
2009-03-10 11:17 ` Peter Korsgaard [this message]
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=87ljrdaapy.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.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