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

--- duma_2_5_12.orig/Makefile	2007-09-07 21:57:45.000000000 +0200

+++ duma_2_5_12/Makefile	2007-09-07 21:58:35.000000000 +0200

@@ -231,9 +231,13 @@

 	dumatest.c tstheap.c thread-test.c testmt.c dumatestpp.cpp testoperators.cpp \

 	createconf.c

-OBJECTS = dumapp.o duma.o sem_inc.o print.o

+OBJECTS = duma.o sem_inc.o print.o

+SO_OBJECTS = duma_so.o sem_inc_so.o print_so.o

-SO_OBJECTS = dumapp_so.o duma_so.o sem_inc_so.o print_so.o

+ifeq ($(DUMA_CPP),1)

+OBJECTS += dumapp.o

+SO_OBJECTS += dumapp_so.o

+endif

 all:	libduma.a tstheap$(EXEPOSTFIX) dumatest$(EXEPOSTFIX) thread-test$(EXEPOSTFIX) testmt$(EXEPOSTFIX) dumatestpp$(EXEPOSTFIX) testoperators$(EXEPOSTFIX) $(DUMA_DYN_DEPS)

 	@ $(ECHOLF)