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

 # mingw options

 ## depends on WINDOWS

 ##

 ## select LIBC_SUPPORT_WIN32THREADS

 ##

 ## help The de-facto standard for Mingw distributions.

 choice

     bool

     prompt "Windows API version"

 # Don't remove next line

 # CT_INSERT_VERSION_BELOW

 config WINAPI_V_2_0_7

     bool

     prompt "2.0.7"

 config WINAPI_V_select

     bool

     prompt "Other version"

 endchoice

 config WINAPI_VERSION

     string

     prompt "Windows API version" if WINAPI_V_select

 # Don't remove next line

 # CT_INSERT_VERSION_STRING_BELOW

     default "2.0.7" if WINAPI_V_2_0_7

     help

       Enter the version number of the Windows API files to use

 config MINGW_DIRECTX

     bool

     prompt "Include DirectX development files"

 config MINGW_DDK

     bool

     prompt "Include DDK development files"