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_OBSOLETE=y

CT_LOCAL_TARBALLS_DIR="${HOME}/src"

CT_SAVE_TARBALLS=y

CT_LOG_EXTRA=y

CT_ARCH_sh=y

CT_ARCH_SH_SH4=y

CT_KERNEL_linux=y

CT_KERNEL_V_2_6_27_62=y

CT_BINUTILS_V_2_19_1a=y

CT_CC_V_4_3_2=y

CT_CC_LANG_CXX=y

CT_LIBC_glibc=y

CT_LIBC_GLIBC_V_2_9=y

# CT_LIBC_GLIBC_FORCE_UNWIND is not set

CT_GMP_V_4_3_2=y

CT_MPFR_V_2_4_2=y