Adding a compilation define so that on recent Darwin mysqld does not react to SIGHUP and SIGQUIT:
this fixes a rpl000001 problem on our Powermac G5 machine (popping after an upgrade from 10.3.4 to
10.3.5) and is expected to fix 
BUG#2030 "relay bin log on slave resets multiple times a second"
(i.e. under some Mac OS X Panther versions, mysqld receives many SIGHUP and SIGQUIT).
So this fix is more a problem-hider than a real understanding of why mysqld receives so many signals.
Note that we saw other problems on this OS where mysqld reacts to Ctrl-Z but apparently only once,
where using SSL seems to make the problem more frequent...

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

into eagle.mysql.r18.ru:/home/vva/work/BUG_4358/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_4358/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_4973/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_4973/mysql-4.0

   - resorting to having to separate sections for darwin7 and darwin8

       from the select list and TEXT field 

make setup_copy_fields to insert Item_copy_string for blobs in 
the beginning of the copy_funcs (push_back instead of push_front)

the thing is that Item_copy_string::copy for function can call 
Item_copy_string::val_int for blob via Item_ref.
But if Item_copy_string::copy for blob isn't called before, 
it's value will be wrong.

So all the Item_copy_string::copy for blobs should be called before 
Item_copy_string::copy for functions.

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

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

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b4898

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/bug4411

  Fix for server hang bug

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

 - Changed the default log file name to Bootstrap-<repository>.log
   (e.g. Bootstrap-mysql-4.0.log) (thanks to Joerg for the hint)
 - added option "--archive-log" to automatically move the log file
   into the Log directory of the exported tree

   format() around them (as suggested by serg)

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

   applications against the the embedded server libmysqld.a) 
   (BUG#4921)

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

into hundin.mysql.fi:/home/marko/k/mysql-4.0

  os_file_create_tmpfile(): display errno in case of failure

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

into brandersnatch.localdomain:/home/dlenev/src/mysql-4.0-bg4491

  a note to the RPM ChangeLog about it

into mysql.com:/home/mydev/mysql-4.0-4000

Solved performance problems by enabling write buffer.

InnoDB: Implement tmpfile() differently on Windows (Bug #3998)

We should allow 19 as length of newly created TIMESTAMP fields.