allow tokftdump to work on old tokudb files
Fixes Tokutek/ft-index#44 Fix loop counter/array bounds in test_stress0
Refs Tokutek/ft-index#26 Fixes Tokutek/ft-index#31 Change api for *_multiple to support array indexing.  Never call put/del_callback functions for src_db.
refs Tokutek/mongo#399, change hot_optimize to take bounds
Merge branch 'bugs/mongo-399'
refs #48, have ft_flush_some_child still do a flush if the child is a leaf node, so garbage collection happens
guarded new DBT_ARRAY api functions with #ifdef USE_TDB #31

BDB versions of tests fail to compile because DBT_ARRAY is undeclared.
refs #48, remove unnecessary paranoid_invariant
#31 remove more tokudb only tests
guarded new DBT_ARRAY api functions with #ifdef USE_TDB #31

BDB versions of tests fail to compile because DBT_ARRAY is undeclared.
#31 remove more tokudb only tests
Merge branch 'bdb-compile-fix' of github.com:Tokutek/ft-index into bdb-compile-fix
fixes #55, fix test
#50 count long tail events like long fsyncs, checkpoints, and lock tree waits
refs #54, improve the performance of hot indexing. This change does two things:
 - gets indexer to run in reverse, that is, start at the end and run to beginning
 - refines locking a bit. An estimate of the position of the hot indexer is stored,
   that is cheap to look at. Threads that use this estimate with a mutex either do
   only a quick comparison or set it to a new value. Threads doing writes (with XXX_multiple calls)
   will check their position with respect to the estimate, and if they see the hot indexer
   is already past where they will modify, they don't grab the more expensive indexer
   lock. For insertion workloads that go to the end of the main dictionary of a table/collection,
   this check should practically always pass.
refs #36, have the FIFO realloc its buffer on resize, as opposed to malloc and memcpy
#50 count lock tree timeouts
refs #62 fix how tdb_logprint formats XID pairs
fixed required cmake version #65

fixes #65
remove -u option from cp, fixes #66