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://gcc.gnu.org/PR3106

 Backported from gcc-3.0.x

 Fixes error

   .../binutils-2.11.2/libiberty/strerror.c:468: error: conflicting types for `sys_nerr'

   /usr/include/stdio.h:258: error: previous declaration of `sys_nerr'

   make[1]: *** [strerror.o] Error 1

   make: *** [all-libiberty] Error 2

 on Mac OS X.

 --- gcc-2.95.3/libiberty/strerror.c.old	2004-03-24 16:23:19.000000000 -0800

 +++ gcc-2.95.3/libiberty/strerror.c	2004-03-24 16:23:48.000000000 -0800

 @@ -13,6 +13,7 @@

     incompatible with our later declaration, perhaps by using const

     attributes.  So we hide the declaration in errno.h (if any) using a

     macro. */

 +#define sys_nerr sys_nerr__

  #define sys_errlist sys_errlist__

  #endif

 @@ -20,6 +21,7 @@

  #include <errno.h>

  #ifdef HAVE_SYS_ERRLIST

 +#undef sys_nerr

  #undef sys_errlist

  #endif