From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Resume on WGET commands
Date: Fri, 19 Mar 2010 16:16:02 +0100 [thread overview]
Message-ID: <877hp8gx59.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4BA08BFB.4080102@iwtech.com.au> (Paul Jones's message of "Wed, 17 Mar 2010 18:59:55 +1100")
>>>>> "Paul" == Paul Jones <paul.jones@iwtech.com.au> writes:
Hi,
Paul> Is there a reason that buildroot doesn't seem to use the -c
Paul> command for wget by default? It would be quite handy to have.
Not as far as I remember.
Paul> Then I remembered there was an option to modify the wget command
Paul> line in build options and it didn't seem to work.
No? It seems to work here from a quick look. For easy debugging you can
remove the $(Q) from the line just after define DOWNLOAD in
package/Makefile.package.in
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-03-19 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 7:59 [Buildroot] Resume on WGET commands Paul Jones
2010-03-19 15:16 ` Peter Korsgaard [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=877hp8gx59.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