Second platform fix for floating point rounding.

Reduced the precision of the test numbers.
Not all platforms could reproduce the exact numbers.

The problem was an ab-use of last_rkey_length.
Formerly we saved the packed key length (of the search key)
in this element. But in certain cases it got replaced by 
the (packed) result key length.
Now we use a new element of MI_INFO to save the packed key 
length of the search key.

  Delete: man/which.2

Ignored some generated files

Enlarged the counter variables to ulonglong.

Solution for 4.0 and 4.1.
If the caller cannot re-open table(s), it gives a NULL
'refresh' argument to open_table(). We used to ignore
flushes then. Now we ignore drops too.

into  kite-hub.kitebird.com:/tmp/merge-4.0

  Update README (2nd try)

into mysql.com:/M40/mysql-4.0

  Flag -DHAVE_DARWIN_THREADS not needed for darwin9

into  mysql.com:/home/hartmut/projects/mysql/dev/4.0

to be built successfully.

into  selena.:H:/MYSQL/src/#05588-mysql-4.0

  Back port of QNX work around for rint()

  Back port of code to find the right 'ps' settings

read timeout properly on win32.

  Update test result.

  Reorder out-of-order system variables.

into  frost.snake.net:/Volumes/frost2/MySQL/bk/mysql-4.0

  Make ports configurable from environment for test

into  frost.snake.net:/Volumes/frost2/MySQL/bk/mysql-4.0

  Reorder out-of-order status variables.

  Reorder out-of-order system variables.

  Fix bug #12779 : never give a row count estimate of 0 to the MySQL query optimizer, as then left join optimizer may beleive it KNOWS that the table is empty; note that this fix may change query optimization of many other queries where one table is empty; note that the proper fix would be to make the query optimizer to know that the row count estimates it receives really are just estimates, it cannot assume they are certain

against a later version of libc.

into mysql.com:/space/my/mysql-4.0-merge

  preflight/postflight instead, so they are run every time a PKG is installed, not only for
  a fresh installation

  change was too drastic) (BUG#12506)

into  krsna.patg.net:/home/patg/mysql-build/mysql-4.0