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 binutils-2.20.1.orig/libiberty/Makefile.in binutils-2.20.1/libiberty/Makefile.in

 --- binutils-2.20.1.orig/libiberty/Makefile.in	2009-08-23 21:03:58.000000000 +0200

 +++ binutils-2.20.1/libiberty/Makefile.in	2010-08-17 19:32:19.000000000 +0200

 @@ -227,6 +227,7 @@

  	  $(AR) $(AR_FLAGS) $(TARGETLIB) \

  	    $(REQUIRED_OFILES) $(EXTRA_OFILES) $(LIBOBJS); \

  	  $(RANLIB) $(TARGETLIB); \

 +	  cp $(TARGETLIB) ../ ; \

  	  cd ..; \

  	else true; fi