crosstool-ng: patches/binutils/2.17a/180-psignal.patch@333d3e40cbd1

scripts: refine static linking check to better guide the user

The current mechanism to check if static linking is possible, and the mesage
displayed on failure, can be puzzling to the unsuspecting user.

Also, the current implementation is not using the existing infrastructure,
and is thus difficult to enhance with new tests.

So, switch to using the standard CT_DoExecLog infra, and use four tests to
check for the host compiler:
- check we can run it
- check it can build a trivial program
- check it can statically link that program
- check if it statically link with libstdc++

That should cover most of the problems. Hopefully.

(At the same time, fix a typo in a comment)

Signed-off-by: Daniel Price <daniel.price@gmail.com>
[yann.morin.1998@free.fr: split original patch for self-contained changes]
[yann.morin.1998@free.fr: use steps to better see gcc's output]
[yann.morin.1998@free.fr: commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <163f86b5216fc08c672a.1353459722@nipigon.dssd.com>
Patchwork-Id: 200536

     1 Make psignal prototype in libiberty match that in glibc.

     3 Fixes:

     5 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c: In function `psignal':

     6 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `signo' doesn't match prototype

     7 /usr/include/signal.h:131: prototype declaration

     8 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:563: argument `message' doesn't match prototype

     9 /usr/include/signal.h:131: prototype declaration

    10 gcc-2.95.3-glibc-2.1.3/binutils-2.15/libiberty/strsignal.c:568: warning: comparison between signed and unsigned

    11 mprotect... make[1]: *** [strsignal.o] Error 1

    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'

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

    15 when building on red hat 7.1

    16 though it's a bit of a mystery why libiberty's psignal is being compiled at

    17 all, since red hat 7.1's glibc supports psignal (hence the error message)

    19 --- binutils-2.17/libiberty/strsignal.c.old	2005-04-18 13:57:40.000000000 -0700

    20 +++ binutils-2.17/libiberty/strsignal.c	2005-04-18 13:59:09.000000000 -0700

    21 @@ -536,7 +536,7 @@

    23  /*

    25 -@deftypefn Supplemental void psignal (unsigned @var{signo}, char *@var{message})

    26 +@deftypefn Supplemental void psignal (int @var{signo}, const char *@var{message})

    28  Print @var{message} to the standard error, followed by a colon,

    29  followed by the description of the signal specified by @var{signo},

author	Daniel Price <daniel.price@gmail.com>
	Tue Nov 20 16:59:17 2012 -0800 (2012-11-20)
changeset 3126	333d3e40cbd1
parent 747	d3e603e7c17c
permissions	-rw-r--r--