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

 http://mirror.sh-linux.org/rpm-2003/SRPMS/gcc-3.2.3-3.src.rpm contains the following patches:

 gcc-20030210-sh-linux-1.patch

 gcc-3.2.3-libffi-1.patch

 gcc-3.2.3-sh-linux-dwarf2-1.patch (*not* applied by the spec file, it's in there by accident)

 gcc-3.2.3-libffi-1.patch was needed just to build, I think.

 After that was applied, sh4 gcc seemed to compile fine, but c++ programs

 failed to execute because libstdc++.so.5 was built without version

 info.  This was caused directly by libstdc++-v3/configure setting

 SYMVER_MAP=config/linker-map.dummy because it sees that 

 no libgcc_s.so was generated; configure says

   checking for shared libgcc... no.

 Applying gcc-20030210-sh-linux-1.patch in hopes it makes those problems go away.