configure: add possibility to set arbitrary variable in check_for

If check_for is able to find the required prog/inc/lib, allow it to
set an arbitrary variable to 'y'. This variable is then pushed down
to the kconfig definition.

For example:
has_or_abort prog=foobar kconfig=has_foobar

If foobar is available, it yields a kconfig variable defaulting to y:
config CONFIGURE_has_foobar
bool
default y

If foobar is missing, it yields a kconfig variable defaulting to n:
config CONFIGURE_has_foobar
bool

Thus it is possible to depends on that variabel to show/hide options:
config SOME_FEATURE
bool
prompt "Some feature"
depends on CONFIGURE_has_foobar

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

diff -durN gcc-4.4.5.orig/gcc/config/arm/linux-eabi.h gcc-4.4.5/gcc/config/arm/linux-eabi.h

--- gcc-4.4.5.orig/gcc/config/arm/linux-eabi.h	2007-11-08 14:44:09.000000000 +0100

+++ gcc-4.4.5/gcc/config/arm/linux-eabi.h	2010-10-09 23:01:59.000000000 +0200

@@ -44,7 +44,7 @@

    The ARM10TDMI core is the default for armv5t, so set

    SUBTARGET_CPU_DEFAULT to achieve this.  */

 #undef  SUBTARGET_CPU_DEFAULT

-#define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm10tdmi

+#define SUBTARGET_CPU_DEFAULT TARGET_CPU_arm9tdmi

 /* TARGET_BIG_ENDIAN_DEFAULT is set in

    config.gcc for big endian configurations.  */