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

CT_EXPERIMENTAL=y

CT_LOCAL_TARBALLS_DIR="${HOME}/src"

CT_SAVE_TARBALLS=y

CT_LOG_EXTRA=y

CT_ARCH_mips=y

CT_TARGET_VENDOR="malta"

CT_KERNEL_linux=y

CT_KERNEL_V_2_6_38_8=y

CT_BINUTILS_V_2_21_1a=y

CT_CC_V_4_4_6=y

# CT_CC_GCC_USE_GRAPHITE is not set

CT_LIBC_EGLIBC_V_2_13=y

CT_DEBUG_gdb=y

# CT_GDB_GDBSERVER_STATIC is not set

CT_GDB_V_7_2a=y

CT_GMP_V_5_0_1=y

CT_MPFR_V_3_0_0=y

CT_TEST_SUITE_GCC=y