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 -dur binutils-2.17.old/bfd/opncls.c binutils-2.17/bfd/opncls.c

 --- binutils-2.17.old/bfd/opncls.c	2006-03-16 13:20:16.000000000 +0100

 +++ binutils-2.17/bfd/opncls.c	2007-05-01 18:26:11.000000000 +0200

 @@ -158,6 +158,13 @@

  {

    bfd *nbfd;

    const bfd_target *target_vec;

 +  struct stat s;

 +

 +  if (stat (filename, &s) == 0)

 +    if (S_ISDIR(s.st_mode)) {

 +      bfd_set_error (bfd_error_file_not_recognized);

 +      return NULL;

 +    }

    nbfd = _bfd_new_bfd ();

    if (nbfd == NULL)