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

reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"

reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"

reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g., MPC8548,

MPC8572). It uses eglibc (for e500/SPE patches) and a recent gcc (4.6.0,

for e500v2 DPFP support) and will generate appropriate dual-precision

floating point instructions by default.

Note: If building a Linux kernel with this toolchain, you will want to make

sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE ABI/instructions

from getting into the kernel (which is currently unsupported). At this time,

the kernel build system properly passes those two options, but older kernels

were only passing -mno-spe by default."