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

 # 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

 }