From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000646]: Buildroot can't download gcc
Date: Mon, 12 Feb 2007 05:49:24 -0800 [thread overview]
Message-ID: <1d5495541f41b3b7c4e5dfe4e183c022@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=646
======================================================================
Reported By: jslyster
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 646
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 01-17-2006 07:45 PST
Last Modified: 02-12-2007 05:49 PST
======================================================================
Summary: Buildroot can't download gcc
Description:
Buildroot cannot download gcc because the server at mirrors.rcn.net isn't
up. mirrors.rcn.net hasn't been up for at least a week, and possibly much
more time than that.
======================================================================
----------------------------------------------------------------------
scott - 01-18-06 08:17
----------------------------------------------------------------------
This is what we are now using....
#GCC_SITE:=ftp://ftp.gnu.org/gnu/gcc/releases/gcc-$(GCC_VERSION)
#GCC_SITE:=http://mirrors.rcn.net/pub/sourceware/gcc/releases/gcc-$(GCC_VERSION)
GCC_SITE:=ftp://mirrors.laffeycomputer.com/pub/gcc.gnu.org/pub/gcc/releases/gcc-$(GCC_VERSION)
----------------------------------------------------------------------
prpplague - 01-19-06 07:08
----------------------------------------------------------------------
GCC_SITE:=ftp://ftp.ibiblio.org/pub/mirrors/gnu/ftp/gnu/gcc/gcc-$(GCC_VERSION)
was fixed with 13394
Issue History
Date Modified Username Field Change
======================================================================
01-17-06 07:45 jslyster New Issue
01-17-06 07:45 jslyster Status new => assigned
01-17-06 07:45 jslyster Assigned To => uClibc
01-18-06 08:17 scott Note Added: 0000946
01-19-06 07:08 prpplague Note Added: 0000954
01-19-06 07:08 prpplague Status assigned => closed
01-19-06 07:08 prpplague Resolution open => fixed
02-12-07 05:49 vapier Status closed => assigned
02-12-07 05:49 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1d5495541f41b3b7c4e5dfe4e183c022@bugs.busybox.net \
--to=bugs@busybox.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