scripts: unset CONFIG_SITE

Some distributions (eg. openSUSE 12.1) systematically export
the CONFIG_SITE environment variable to point to a custom
script setting misc paths for ./configure.

This can, and does, break when cross-compiling for architectures
that are not supported by this script.

The simple workaround is to unset this variable.
NB: buildroot has a similar fix:
http://git.buildroot.org/buildroot/commit/?id=12c9f7dd6dee9c6029b4f9a12d6aac1516911ab4

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 21f4f28e60ec0342133086c9a51e7f0e5b181fb8)

diff -durN gcc-4.4.4.orig/boehm-gc/include/gc.h gcc-4.4.4/boehm-gc/include/gc.h

--- gcc-4.4.4.orig/boehm-gc/include/gc.h	2007-04-23 23:10:09.000000000 +0200

+++ gcc-4.4.4/boehm-gc/include/gc.h	2010-05-16 19:36:48.000000000 +0200

@@ -503,7 +503,7 @@

 #if defined(__linux__) || defined(__GLIBC__)

 # include <features.h>

 # if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1 || __GLIBC__ > 2) \

-     && !defined(__ia64__)

+     && !defined(__ia64__) && !defined(__UCLIBC__)

 #   ifndef GC_HAVE_BUILTIN_BACKTRACE

 #     define GC_HAVE_BUILTIN_BACKTRACE

 #   endif