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 -dur strace-4.5.16.orig/syscall.c strace-4.5.16/syscall.c

 --- strace-4.5.16.orig/syscall.c	2007-07-14 19:21:44.000000000 +0200

 +++ strace-4.5.16/syscall.c	2007-07-14 19:22:49.000000000 +0200

 @@ -125,6 +125,18 @@

  #define TP TRACE_PROCESS

  #define TS TRACE_SIGNAL

 +#ifndef HAVE_STATFS64

 +/*

 + * Ugly hacks for systems that do not have LFS

 + */

 +

 +#define sys_truncate64  sys_truncate

 +#define sys_ftruncate64 sys_ftruncate

 +#define sys_getdents64  sys_getdents

 +#define sys_statfs64    sys_statfs

 +#define sys_fstatfs64   sys_fstatfs

 +#endif

 +

  static const struct sysent sysent0[] = {

  #include "syscallent.h"

  };