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(-)

 # Wrapper to build the tools facilities

 # List all tools facilities, and parse their scripts

 CT_TOOLS_FACILITY_LIST=

 for f in "${CT_LIB_DIR}/scripts/build/tools/"*.sh; do

     is_enabled=

     . "${f}"

     f=$(basename "${f}" .sh)

     if [ "${is_enabled}" = "y" ]; then

         CT_TOOLS_FACILITY_LIST="${CT_TOOLS_FACILITY_LIST} ${f#???-}"

     fi

 done

 # Download the tools facilities

 do_tools_get() {

     for f in ${CT_TOOLS_FACILITY_LIST}; do

         do_tools_${f}_get

     done

 }

 # Extract and patch the tools facilities

 do_tools_extract() {

     for f in ${CT_TOOLS_FACILITY_LIST}; do

         do_tools_${f}_extract

     done

 }

 # Build the tools facilities

 do_tools() {

     for f in ${CT_TOOLS_FACILITY_LIST}; do

         do_tools_${f}_build

     done

 }