From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc compilation issues on AT91SAM9G20
Date: Fri, 27 Feb 2009 12:35:59 +0100 [thread overview]
Message-ID: <874oygm7s0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090227194950.a345c8d5.william@brodie-tyrrell.org> (William Brodie-Tyrrell's message of "Fri\, 27 Feb 2009 19\:49\:50 +0900")
>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:
>> Ehh, that's because we don't have a wget.sh (and never had) - Where do
>> you see any references to a wget.sh?
William> When I run make, it seems to use that to download the sources. If it's not there, make fails while trying to download sources. On second-look, it seems that the .config file provided by linux4sam has this line in it:
William> BR2_WGET="$(TOPDIR)/scripts/wget.sh $(BR2_WGET_MIRROR) --passive-ftp --retry-connrefused --waitretry=10"
Ahh, that must be from the atmel patch. I think I remember something
about a wget.sh in HcE's avr32 tree.
delete the BR2_WGET line in your .config and run make oldconfig and it
should be fixed.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-02-27 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 8:44 [Buildroot] native toolchain compilation problem William Brodie-Tyrrell
2009-02-25 9:28 ` Peter Korsgaard
2009-02-25 10:12 ` William Brodie-Tyrrell
2009-02-25 10:18 ` Peter Korsgaard
2009-02-26 6:15 ` [Buildroot] gcc compilation issues on AT91SAM9G20 William Brodie-Tyrrell
2009-02-27 9:15 ` Peter Korsgaard
2009-02-27 10:07 ` William Brodie-Tyrrell
2009-02-27 10:37 ` Peter Korsgaard
2009-02-27 10:49 ` William Brodie-Tyrrell
2009-02-27 11:35 ` 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=874oygm7s0.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