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

On 20081011, Khem RAJ writes:

 You have to bar gcc trying to build unwinding at stage 1. Try the

 attached patch and see if it helps.

 gcc/config/sh/linux-unwind.h |    3 +++

 1 file changed, 3 insertions(+)

Index: gcc-4_2-branch/gcc/config/sh/linux-unwind.h

===================================================================

--- gcc-4_2-branch.orig/gcc/config/sh/linux-unwind.h	2008-07-01 17:24:40.000000000 -0700

+++ gcc-4_2-branch/gcc/config/sh/linux-unwind.h	2008-07-01 17:25:47.000000000 -0700

@@ -26,6 +26,8 @@ along with this program; see the file CO

 the Free Software Foundation, 51 Franklin Street, Fifth Floor,

 Boston, MA 02110-1301, USA.  */

+#ifndef inhibit_libc

+

 /* Do code reading to identify a signal frame, and set the frame

    state data appropriately.  See unwind-dw2.c for the structs.  */

@@ -251,3 +253,4 @@ sh_fallback_frame_state (struct _Unwind_

   return _URC_NO_REASON;

 }

 #endif /* defined (__SH5__) */

+#endif /* ifndef inhibit_libc */