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

--- gdb-6.1.1-dist/readline/configure	2003-05-27 18:29:47.000000000 -0500

+++ gdb-6.1.1/readline/configure	2004-08-09 14:20:23.000000000 -0500

@@ -6249,7 +6249,12 @@

 echo "$as_me:$LINENO: checking for mbstate_t" >&5

+echo $ECHO_N "bash_cv_have_mbstate_t=$bash_cv_have_mbstate_t" >&6

 echo $ECHO_N "checking for mbstate_t... $ECHO_C" >&6

+if test "${bash_cv_have_mbstate_t+set}" != set; then

+  bash_cv_have_mbstate_t=yes

+  echo $ECHO_N "WARNING!! forcing to yes!!! $ECHO_C" >&6

+fi

 if test "${bash_cv_have_mbstate_t+set}" = set; then

   echo $ECHO_N "(cached) $ECHO_C" >&6

 else