Push the calculation of the tuple's kernel part down to kernel's build scripts:
- update the kernel script's API with the function CT_DiKernelTupleValues
- update doc accordingly (also with the architecture change, missing in the previous commit)
- small clean-up in the main script, remove useless test

/trunk/scripts/build/kernel/bare-metal.sh | 5 5 0 0 +++++
/trunk/scripts/build/kernel/linux.sh | 5 5 0 0 +++++
/trunk/scripts/crosstool.sh | 31 13 18 0 +++++++++++++------------------
/trunk/scripts/functions | 15 8 7 0 ++++++++-------
/trunk/docs/overview.txt | 13 9 4 0 +++++++++----
5 files changed, 40 insertions(+), 29 deletions(-)

 --- gdb-6.1.1-dist/readline/configure	2003-05-27 18:29:47.000000000 -0500

 +++ gdb-6.1.1/readline/configure	2004-08-09 14:20:23.000000000 -0500

 @@ -6249,7 +6249,12 @@

  echo "$as_me:$LINENO: checking for mbstate_t" >&5

 +echo $ECHO_N "bash_cv_have_mbstate_t=$bash_cv_have_mbstate_t" >&6

  echo $ECHO_N "checking for mbstate_t... $ECHO_C" >&6

 +if test "${bash_cv_have_mbstate_t+set}" != set; then

 +  bash_cv_have_mbstate_t=yes

 +  echo $ECHO_N "WARNING!! forcing to yes!!! $ECHO_C" >&6

 +fi

  if test "${bash_cv_have_mbstate_t+set}" = set; then

    echo $ECHO_N "(cached) $ECHO_C" >&6

  else