Simple fixes/optimization of things discovered during review of new pushed code

  If one tries to drop an InnoDB table without an .ibd file, print to .err log that we DID remove the table from the internal data dictionary of InnoDB, and return DB_SUCCESS so that MySQL will delete the .frm file; the drawback in this is that then DROP TABLE returns success, and the user is not alerted; maybe it could return a warning

  Look for 'client_test' in tests/ not bin/
make_binary_distribution.sh:
  Copy 'client_test' into the dist

into a193-229-222-2.elisa-laajakaista.fi:/home/my/bk/mysql-4.1

binary for mysqld_multi was not found. This is because it is
possible to define one under each mysqldN group separately.
Bailing out if mysqld binary is not found at all.

Added option --silent to turn off warnings.

doesn't need to have it's own recovery mechanism.

into hundin.mysql.fi:/home/heikki/mysql-4.1

  Fix bug #5975 about UTF-8 chars and prefix indexes; do not print warnings if a column prefix is > 255 bytes

  To make client_test work as mysql-test-run test case, needs to install it

into mysql.com:/media/sda1/mysql/mysql-4.1-5748-anew

crashes mysqld": implementation for a generic item tree modifications
registry. Every item tree modification which should be rolled back for
subsequent execution of a prepared statement or stored procedure should
be saved in the registry. All such modifications are rolled back at once
during cleanup stage of PS.
Actual fix for the bug just adds a call to register modifications to
convert_constant_item.
Post review fixes implemented.

into a80-186-41-201.elisa-laajakaista.fi:/home/my/bk/mysql-4.1

  Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)

 - Updated Docs/Makefile.am and scripts/make_win_src_distribution.sh
   accordingly

into mysql.com:/space/my/mysql-4.1-build

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

  ...

  Merge manually the InnoDB mysqldump -l crash patch (crash with LOCK TABLES ... LOCAL) from 4.0 to 4.1; some code cleanup

into mysql.com:/space/my/mysql-4.1-build

into mysql.com:/home/my/mysql-4.1

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

function being used before it was defined - "forward" declaration
was insufficient.

differently when converting column to auto_increment in 4.1" with
current tree.

into mysql.com:/home/my/mysql-4.1

into mysql.com:/home/my/mysql-4.1

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

to auto_increment in 4.1".
Now we are enforcing NO_AUTO_VALUE_ON_ZERO mode during ALTER TABLE only
if we are converting one auto_increment column to another auto_increment
column (this also includes most common case when we don't do anything
with such column).

Also now when we convert some column to TIMESTAMP NOT NULL column with
ALTER TABLE we convert NULL values to current timestamp, (as we do this
in INSERT). One can still get old behavior by setting system TIMESTAMP
variable to 0.

into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1

Some bigger code changes was necessary becasue of the multi-table-update and the new HANDLER code