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 ARM-specific values

 CT_DoArchValues() {

     # The architecture part of the tuple:

     CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"

     # The system part of the tuple:

     case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in

         glibc,)     CT_TARGET_SYS=gnu;;

         glibc,y)    CT_TARGET_SYS=gnueabi;;

         uClibc,)    CT_TARGET_SYS=uclibc;;

         uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;

     esac

 }