From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain support improvements
Date: Tue, 4 Nov 2008 00:51:39 +0100 [thread overview]
Message-ID: <200811040051.40880.markus.heidelberg@web.de> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909C91465@mi8nycmail19.Mi8.com>
hartleys, 03.11.2008:
> BTW, something is now broken with svn revision 23911 using an external
> toolchain.
>
> I just did a "svn up; make menuconfig; make" and I get the following
> errors right when the build starts.
>
> wget --passive-ftp -nd -P /home/bigguiness/buildroot/dl
> "http://www.kernel.org/pub/"/linux/kernel/v2.6//linux-...tar.bz2
> --08:47:11--
> http://www.kernel.org/pub//linux/kernel/v2.6//linux-...tar.bz2
> => `/home/bigguiness/buildroot/dl/linux-...tar.bz2'
> Resolving www.kernel.org... 204.152.191.5, 204.152.191.37
> Connecting to www.kernel.org|204.152.191.5|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 08:47:11 ERROR 404: Not Found.
>
> make: *** [/home/bigguiness/buildroot/dl/linux-...tar.bz2] Error 1
>
>
> I can't figure out what .mk is trying to download "linux-...tar.bz2".
> Any ideas?
Some odd configuration?
grep WGET target/linux/Makefile.in*
Find out which one is used and backtrace the variable. Probably some kernel
version number variables are empty resulting in .. instead of 2.6.25
Markus
next prev parent reply other threads:[~2008-11-03 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 8:45 [Buildroot] External toolchain support improvements Thomas Petazzoni
2008-10-31 18:42 ` hartleys
2008-11-03 8:31 ` Thomas Petazzoni
2008-11-03 15:52 ` hartleys
2008-11-03 23:51 ` Markus Heidelberg [this message]
2008-10-31 19:21 ` Grant Likely
2008-11-03 10:15 ` Peter Korsgaard
2008-11-03 10:18 ` Peter Korsgaard
2008-11-03 12:48 ` Shinya Kuribayashi
2008-11-03 12:58 ` Peter Korsgaard
2008-11-03 13:25 ` Shinya Kuribayashi
2008-11-03 14: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=200811040051.40880.markus.heidelberg@web.de \
--to=markus.heidelberg@web.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