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>

Original patch from Gentoo.

-= BEGIN original header =-

-= END original header =-

diff -durN uClibc-0.9.30.orig/libc/sysdeps/linux/arm/bits/uClibc_arch_features.h uClibc-0.9.30/libc/sysdeps/linux/arm/bits/uClibc_arch_features.h

--- uClibc-0.9.30.orig/libc/sysdeps/linux/arm/bits/uClibc_arch_features.h	2008-09-25 10:50:56.000000000 +0200

+++ uClibc-0.9.30/libc/sysdeps/linux/arm/bits/uClibc_arch_features.h	2009-02-07 09:57:59.000000000 +0100

@@ -39,4 +39,8 @@

 /* define if target supports IEEE signed zero floats */

 #define __UCLIBC_HAVE_SIGNED_ZERO__

+#ifdef __ARM_EABI__

+# define __UCLIBC_TRUNCATE64_HAS_4_ARGS__

+#endif

+

 #endif /* _BITS_UCLIBC_ARCH_FEATURES_H */