Using SOCKS 4/5 proxy is no easy task:
- a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate)
- tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection
- SOCKS proxies are expected to be in 'local' networks
- there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in

Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed.

/trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++----
/trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------
2 files changed, 77 insertions(+), 14 deletions(-)

# Compute x86-specific values

# This one really need a little love! :-(

CT_DoArchValues() {

    # The architecture part of the tuple:

    arch="${CT_ARCH_ARCH}"

    [ -z "${arch}" ] && arch="${CT_ARCH_TUNE}"

    case "${arch}" in

        nocona|athlon*64|k8|athlon-fx|opteron)

            CT_DoError "Architecture is x86 (32-bit) but selected processor is \"${arch}\" (64-bit)";;

        "")                           CT_TARGET_ARCH=i386;;

        i386|i486|i586|i686)          CT_TARGET_ARCH="${arch}";;

        winchip*)                     CT_TARGET_ARCH=i486;;

        pentium|pentium-mmx|c3*)      CT_TARGET_ARCH=i586;;

        pentiumpro|pentium*|athlon*)  CT_TARGET_ARCH=i686;;

        *)                            CT_TARGET_ARCH=i586;;

    esac

    # The kernel ARCH:

    CT_KERNEL_ARCH=i386

}