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 duma_2_5_8.orig/Makefile duma_2_5_8/Makefile

--- duma_2_5_8.orig/Makefile	2007-08-17 09:34:25.000000000 +0200

+++ duma_2_5_8/Makefile	2007-09-07 21:50:04.000000000 +0200

@@ -93,9 +93,6 @@

 # also define 'WIN32'

 # some defaults:

-CC=gcc

-CXX=g++

-AR=ar

 INSTALL=install

 RM=rm

 RMFORCE=rm -f

@@ -281,7 +278,7 @@

 createconf$(EXEPOSTFIX): createconf.o

 	- $(RMFORCE) createconf$(EXEPOSTFIX)

-	$(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

+	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

 tstheap$(EXEPOSTFIX): libduma.a tstheap.o

 	- $(RMFORCE) tstheap$(EXEPOSTFIX)

@@ -338,7 +335,7 @@

 # define rules how to build objects for createconf

 #

 createconf.o:

-	$(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@

+	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@

 #