"Can't make example storage engine available"
Build was attempting a shared-lib build instead of static

now using CONFIGURE_FILE and INCLUDE to generate handlerton.cc and to set the definitions based on
the storage engines given on the command line

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new

into  mysql.com:/home/ndbdev/skozlov/mysql-5.1-new

into  mysql.com:/space/pekka/ndb/version/my51

into  mysql.com:/home/kgeorge/mysql/5.1/B15102

  Reproduced in 5.0.16-nt. Tested to work in 5.0.20
  

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

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

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

  Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert()
    Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args)

into  zim.(none):/home/brian/mysql/dep-5.1

into  mysql.com:/home/dlenev/mysql-5.1-merges

into  mysql.com:/home/dlenev/mysql-5.1-merges

  AC_ARG_WITH inside "if" sometimes gives unexpected result,
  --with-fast-mutexes was not ignored when --with-debug given

into lmy004.:/work/mysql-5.1-bug16415

into lmy004.:/work/mysql-5.1-bug16415

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

into  mysql.com:/home/dlenev/mysql-5.1-merges

into  mysql.com:/home/dlenev/mysql-5.1-merges

into  c-8808e253.1238-1-64736c10.cust.bredbandsbolaget.se:/home/pappa/bug18198

Review fixes

into  c-8808e253.1238-1-64736c10.cust.bredbandsbolaget.se:/home/pappa/bug18198

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

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

If the WHERE condition of a query contained an ORed FALSE term
then the set of tables whose rows cannot serve for null complements
in outer joins was determined incorrectly. It resulted in blocking 
possible conversions of outer joins into joins for such queries.

tables corrupt triggers".

It turned out that we also have relied at certain places that
(new_table != table_name) were always true on Windows and for transactional
tables. Since our fix for the bug brakes this assumption we have to add new
flag to pass this information around.
This code needs to be refactored but I dare not to do this in 5.0.

into  mysql.com:/home/dlenev/mysql-5.1-merges