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

 See http://sources.redhat.com/ml/binutils/2004-06/msg00114.html

 --- src/bfd/elflink.c.org	2004-07-05 09:11:42.920597000 -0400

 +++ src/bfd/elflink.c	2004-07-05 09:12:59.240847000 -0400

 @@ -2700,7 +2700,7 @@

      return vdiff > 0 ? 1 : -1;

    else

      {

 -      long sdiff = h1->root.u.def.section - h2->root.u.def.section;

 +      long sdiff = h1->root.u.def.section->id - h2->root.u.def.section->id;

        if (sdiff != 0)

  	return sdiff > 0 ? 1 : -1;

      }

 @@ -3954,7 +3954,7 @@

  		i = idx + 1;

  	      else

  		{

 -		  long sdiff = slook - h->root.u.def.section;

 +		  long sdiff = slook->id - h->root.u.def.section->id;

  		  if (sdiff < 0)

  		    j = idx;

  		  else if (sdiff > 0)