From: Thomas <tokant@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] AT91RM9200df, some applications depend on libintl/libiconv
Date: Mon, 09 Mar 2009 21:56:54 +0100 [thread overview]
Message-ID: <1236632214.3645.6.camel@bernd-desktop> (raw)
In-Reply-To: <87ljrkf4y5.fsf@macbook.be.48ers.dk>
On Thu, 2009-03-05 at 14:57 +0100, Peter Korsgaard wrote:
> Any special reason why you don't use the busybox wget applet instead?
thank you for this pointer. I choose the "big" wget, because I was not
aware, that there is another "busybox" wget. It works now.
Thanks, Thomas.
prev parent reply other threads:[~2009-03-09 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 23:28 [Buildroot] AT91RM9200df, some applications depend on libintl/libiconv Thomas
2009-03-05 13:57 ` Peter Korsgaard
2009-03-09 20:56 ` Thomas [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=1236632214.3645.6.camel@bernd-desktop \
--to=tokant@gmx.net \
--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