Some people are reposrting that ftp does not work on their network, probably due to proxies, while http does work.
Some (most) of the sites we use toretrieve tarballs have http equivallent for the ftp service. Use http as a failover.
There's no solution for those sites that do not have such an http equivalent.
/trunk/scripts/build/binutils.sh | 5 2 3 0 ++---
/trunk/scripts/build/libc_glibc.sh | 4 2 2 0 ++--
/trunk/scripts/build/libc_uClibc.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/400-ltrace.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/300-gdb.sh | 8 3 5 0 +++-----
/trunk/scripts/build/kernel_linux.sh | 7 2 5 0 ++-----
/trunk/scripts/build/cc_gcc.sh | 6 2 4 0 ++----
/trunk/scripts/build/gmp.sh | 4 1 3 0 +---
8 files changed, 14 insertions(+), 24 deletions(-)
1 # Wrapper to build the debug facilities
3 # List all debug facilities, and parse their scripts
4 CT_DEBUG_FACILITY_LIST=
5 for f in "${CT_LIB_DIR}/scripts/build/debug/"*.sh; do
8 f=$(basename "${f}" .sh)
9 if [ "${is_enabled}" = "y" ]; then
10 CT_DEBUG_FACILITY_LIST="${CT_DEBUG_FACILITY_LIST} ${f#???-}"
14 # Download the debug facilities
16 for f in ${CT_DEBUG_FACILITY_LIST}; do
21 # Extract and patch the debug facilities
23 for f in ${CT_DEBUG_FACILITY_LIST}; do
28 # Build the debug facilities
30 for f in ${CT_DEBUG_FACILITY_LIST}; do