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

 #!/bin/bash

 # This scripts extracts a crosstool-NG configuration from the log file

 # of a toolchain build with crosstool-NG.

 # Usage: cat <logfile> |$0

 awk '

 BEGIN {

   dump = 0;

 }

 $0~/Dumping crosstool-NG configuration: done in.+s$/ {

   dump = 0;

 }

 dump == 1 { $1 = "" }

 dump == 1

 $0~/Dumping crosstool-NG configuration$/ {

   dump = 1;

 }

 ' |cut -d ' ' -f 2-