patches/binutils/2.17/501-binutils-2.15-psignal.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Apr 18 22:16:28 2008 +0000 (2008-04-18)
changeset 451 8a72f9bcf675
permissions -rw-r--r--
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(-)
yann@56
     1
Make psignal prototype in libiberty match that in glibc.
yann@56
     2
yann@56
     3
Fixes:
yann@56
     4
yann@56
     5
gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c: In function `psignal':
yann@56
     6
gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `signo' doesn't match prototype
yann@56
     7
/usr/include/signal.h:131: prototype declaration
yann@56
     8
gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `message' doesn't match prototype
yann@56
     9
/usr/include/signal.h:131: prototype declaration
yann@56
    10
gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:568: warning: comparison between signed and unsigned
yann@56
    11
mprotect... make[1]: *** [strsignal.o] Error 1
yann@56
    12
make[1]: Leaving directory `/export/hda3/dkegel/queue/jobdir.produser_cpsm17/crosstool-0.32/build/i686-unknown-linux-gnu/gcc-2.95.3-glibc-2.1.3/build-binutils/libiberty'
yann@56
    13
make: *** [all-libiberty] Error 2
yann@56
    14
yann@56
    15
when building on red hat 7.1
yann@56
    16
though it's a bit of a mystery why libiberty's psignal is being compiled at
yann@56
    17
all, since red hat 7.1's glibc supports psignal (hence the error message)
yann@56
    18
yann@56
    19
--- binutils-2.17/libiberty/strsignal.c.old	2005-04-18 13:57:40.000000000 -0700
yann@56
    20
+++ binutils-2.17/libiberty/strsignal.c	2005-04-18 13:59:09.000000000 -0700
yann@56
    21
@@ -536,7 +536,7 @@
yann@56
    22
 
yann@56
    23
 /*
yann@56
    24
 
yann@56
    25
-@deftypefn Supplemental void psignal (unsigned @var{signo}, char *@var{message})
yann@56
    26
+@deftypefn Supplemental void psignal (int @var{signo}, const char *@var{message})
yann@56
    27
 
yann@56
    28
 Print @var{message} to the standard error, followed by a colon,
yann@56
    29
 followed by the description of the signal specified by @var{signo},