This is a workaround for build break on first build in MySQL.
We already have a patches to fix this, but they doesn't work, because
MySQL is running autoconf again after mysql/stamp-h1.
So patches applied in mysql/stamp-h1 are gone, and build fails at configure
phase.
Unfortunately i have no idea how to fix it better. In best way, we should
get rid off all patches, and run autoreconf before configure in mysql/stamp-h1.
This would stop running recheck, but it fails during compilation bison stuff.
- the mysql directory now includes a pure mysql 5.1.37 source
- 2 patches for mysql and file .host.tgz added to patches/mysql
- script mycheck moved also from mysql directory to patches dir
- updated appropriate Mafefile's
----------------------------------------------------------------------------------------
Updated info about MySQL 5.1 compilation on Tomato routers by shibby and Hyzoom (BWQ518)
----------------------------------------------------------------------------------------
Info for devs: if you have a problem with compilation then you have to prepare own .host.tgz archive under mysql dorectory.
1) copy mysql directory to other location.
2) run ./configure
3) cp mysql/include/config.h mysql/include/my_config.h
4) compile parts of mysql on the host with the host gcc (non-cross-compile):
make -C mysql/vio
make -C mysql/mysys
make -C mysql/strings
make -C mysql/dbug
make -C mysql/regex
make -C mysql/sql gen_lex_hash
make -C mysql/scripts comp_sql
make -C mysql/extra comp_err
5) copy files:
mysql/sql/gen_lex_hash
mysql/scripts/comp_sql
mysql/extra/comp_err
to mysql/host directory
6) compress host directory as .host.tgz and copy it under tomato router/mysql/ (overwrite existing file)
7) now you should be able to compile mysql
pedro
Michal Obrembski