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

 # MIPS specific config options

 choice

     bool

     prompt "ABI"

 config ARCH_mips_o32

     bool

     prompt "o32"

     depends on ARCH_32

     help

       This is the -mabi=32 gcc option.

 config ARCH_mips_n32

     bool

     prompt "n32"

     depends on ARCH_64

     help

       This is the -mabi=n32 gcc option.

 config ARCH_mips_n64

     bool

     prompt "n64"

     depends on ARCH_64

     help

       This is the -mabi=64 gcc option.

 # Not supported on Linux:

 # o64   : seems related to *BSD

 # eabi  : seems related to bare-metal

 endchoice

 config ARCH_mips_ABI

     string

     default "32"    if ARCH_mips_o32

     default "n32"   if ARCH_mips_n32

     default "64"    if ARCH_mips_n64