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

diff -durN gcc-4.2.1.orig/gcc/config.gcc gcc-4.2.1/gcc/config.gcc

--- gcc-4.2.1.orig/gcc/config.gcc	2007-02-03 06:25:20.000000000 +0100

+++ gcc-4.2.1/gcc/config.gcc	2007-08-03 20:29:52.000000000 +0200

@@ -1964,7 +1964,7 @@

         ;;

 sh-*-elf* | sh[12346l]*-*-elf* | sh*-*-kaos* | \

 sh-*-symbianelf* | sh[12346l]*-*-symbianelf* | \

-  sh-*-linux* | sh[346lbe]*-*-linux* | \

+  sh*-*-linux* | sh[346lbe]*-*-linux* | \

   sh-*-netbsdelf* | shl*-*-netbsdelf* | sh5-*-netbsd* | sh5l*-*-netbsd* | \

    sh64-*-netbsd* | sh64l*-*-netbsd*)

 	tmake_file="${tmake_file} sh/t-sh sh/t-elf"