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 # Template file for a debug utility
3 # Check here wether your debug tool is enabled or not.
4 # This will get redefined over and over again for each tool, so don't
5 # count on it in the functions below.
6 is_enabled="${CT_FOOBAR}"
8 # Small function to print the filename
9 # Note that this function gets redefined over and over for each tool
10 # It's of no use when building the toolchain proper, but shows all its
11 # usefullness when saving the toolchain and building the tarball.
12 # You shall not echo anything if you're not enabled!
13 # Echo the name of the file, without the extension, below.
16 # [ "${CT_FOOBAR}" = "y" ] || return 0
17 # echo "foobar-${CT_FOOBAR_VERSION}"
21 # Put your download code here
22 do_debug_foobar_get() {
24 # CT_GetFile "foobar-${CT_FOOBAR_VERSION}" http://foobar.com/releases/
28 # Put your extract code here
29 do_debug_foobar_extract() {
31 # CT_ExtractAndPatch "foobar-${CT_FOOBAR_VERSION}"
35 # Put your build code here
36 do_debug_foobar_build() {
38 # mkdir -p "${CT_BUILD_DIR}/build-foobar"
39 # CT_Pushd "${CT_BUILD_DIR}/build-foobar"
40 # "${CT_SRC_DIR}/foobar-${CT_FOOBAR_VERSION}/configure" \
41 # --build=${CT_BUILD} \
42 # --host=${CT_TARGET} \
46 # make DESTDIR="${CT_SYSROOT_DIR}" install