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

 Signed-off-by: dank@kegel.com

 Raising the size of the hash table is a noticable win when linking 

 at least one large app.  

 There was a patch,

 http://sources.redhat.com/ml/binutils/2004-06/msg00165.html

 to do this dynamically.  No idea why that didn't make it in.

 So this tiny change to raise the default size is just

 a stopgap for now.

 --- binutils-2.17/bfd/hash.c.old	2006-03-02 23:01:39.000000000 -0800

 +++ binutils-2.17/bfd/hash.c	2006-03-02 23:01:58.000000000 -0800

 @@ -298,7 +298,7 @@

  */

  /* The default number of entries to use when creating a hash table.  */

 -#define DEFAULT_SIZE 4051

 +#define DEFAULT_SIZE 32749

  static size_t bfd_default_hash_table_size = DEFAULT_SIZE;

  /* Create a new hash table, given a number of entries.  */