Certain updates of table joined to self results in unexpected
behavior.

The problem was that record cache was mistakenly enabled for
self-joined table updates. Normally record cache must be disabled
for such updates.

Fixed wrong condition in code that determines whether to use
record cache for self-joined table updates.

Only MyISAM tables were affected.

into  mysql.com:/usr/home/ram/work/4.1.b6880

into  mysql.com:/usr/home/ram/work/4.1.b16546

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1

  Dont be too aggressive in Dbtc::nodeFailCheckTransaction
  let it timeout by 1, so that it does not assert that it has waited too long
  old impl. set timeotu value to 0, making timeout = (ctcTimer - 0) which could be quite big.

into  mysql.com:/home/marty/MySQL/mysql-4.1

into  rurik.mysql.com:/home/igor/mysql-4.1

refers to a column name.

  Convert to DOS EOL if dsp/dsw is in package

into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new

into  rurik.mysql.com:/home/igor/dev/mysql-4.1-0

refining the test case to exclude problems with koi8r on some platforms.

refers to a column name.
Added a new error message ER_INDEX_DOES_NOT_EXIST.

into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new

into  mysql.com:/usr/home/ram/work/4.1.b16900

into  dl145h.mysql.com:/tmp/andrei/4.1-bug14157-utf8_binlog_testcases

into  production.mysql.com:/usersnfs/rkalimullin/4.1.b18351

  Update NDB version as well

  Stepped up to 4.1.22

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1

into  production.mysql.com:/usersnfs/rkalimullin/4.1.b18351

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1

  Solaris sh don't like {..} in file matching

into  mysql.com:/usr/home/ram/work/4.1.b18536

into mysql.com:/home/hf/work/mysql-4.1.clean

  Always compile position independent

fixing an issue with the test portability.

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1

 - A segfault occured when the function 'kill_server' called 
   'my_sigset' with signal number 0. 'my_sigset' is a macro which
   uses 'sigaction' to install the signal handler with an invalid
   signal number will on most platforms return EINVAL but yields
   a segfauilt on IRIX 6.5
 - The server crash was detected by mysqld_safe and it was restarted although
   a shutdown was requested. 
 - Semantics of kill_server(0) is not known, leaving it intact