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

 Correctly check for g++ existence.

 Copyright 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>

 Licensed to you as dmalloc-5.5.2 is.

 diff -dur dmalloc-5.5.2.orig/configure dmalloc-5.5.2/configure

 --- dmalloc-5.5.2.orig/configure	2007-05-18 11:40:31.000000000 +0200

 +++ dmalloc-5.5.2/configure	2007-05-18 11:42:02.000000000 +0200

 @@ -2643,7 +2643,7 @@

  # see if we actually have a CXX program

 -if test "$ac_cv_prog_CXX" = "" -o ! -x "$ac_cv_prog_CXX"; then

 +if test "$ac_cv_prog_CXX" = "" -o ! -x `which "$ac_cv_prog_CXX"`; then

      { echo "$as_me:$LINENO: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&5

  echo "$as_me: WARNING: could not find C++ compiler $ac_cv_prog_CXX" >&2;}

      enable_cxx=no