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>

 # Compute powerpc-specific values

 CT_DoArchTupleValues () {

     # The architecture part of the tuple, override only for 64-bit

     if [ "${CT_ARCH_64}" = "y" ]; then

         CT_TARGET_ARCH="powerpc64"

     fi

     # Add spe in the tuple if needed

     case "${CT_LIBC},${CT_ARCH_POWERPC_SPE}" in

         glibc,|eglibc,)   CT_TARGET_SYS=gnu;;

         glibc,y|eglibc,y) CT_TARGET_SYS=gnuspe;;

     esac

     # Add extra flags for SPE if needed

     if [ "${CT_ARCH_POWERPC_SPE}" = "y" ]; then

         CT_ARCH_TARGET_CFLAGS="-mabi=spe -mspe"

         CT_ARCH_CC_CORE_EXTRA_CONFIG="--enable-e500_double"

         CT_ARCH_CC_EXTRA_CONFIG="--enable-e500_double"

     fi

 }