binutils: split binutils to backend/frontend, a-la cc_core

Move the actual binutils code to a backend function that builds the
required combo of build/host/target as requested by a frontend.

This split is currently a no-op, but is required for the upcoming
canadian-cross rework, where we'll be needing to build two binutils,
one for build/build/target, and one for build/host/target.

This applies to the three binutils:
- GNU binutils
- elf2flt
- sstrip

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

diff -durN gcc-4.4.5.orig/libstdc++-v3/include/c_global/cstdio gcc-4.4.5/libstdc++-v3/include/c_global/cstdio

--- gcc-4.4.5.orig/libstdc++-v3/include/c_global/cstdio	2009-04-10 01:23:07.000000000 +0200

+++ gcc-4.4.5/libstdc++-v3/include/c_global/cstdio	2010-10-09 23:11:27.000000000 +0200

@@ -139,7 +139,7 @@

 _GLIBCXX_END_NAMESPACE

-#if _GLIBCXX_USE_C99

+#if _GLIBCXX_USE_C99 || defined __UCLIBC__

 #undef snprintf

 #undef vfscanf