MySQL libraries and client drivers
Before you begin
If you are using MySQL 5.1, you must use the MySQL 5.0 client.
If you are installing MySQL on the same host as the Build Forge host, install the following:
MySQL database server
MySQL-client-community-5.0.51a-0.rhel5.i386 - client drivers
MySQL-shared-compat-5.0.51a-0.rhel5.i386 - required compatibility libraries
Connector/J JDBC driverIf you are installing MySQL on a different host, install the following on the Build Forge host:
MySQL-client-community-5.0.51a-0.rhel5.i386 - client drivers
MySQL-shared-compat-5.0.51a-0.rhel5.i386 - required compatibility libraries
Connector/J JDBC driverFor AIX systems only:
You must install the Connector/J driver and the 5.0-51a client drivers. They are compatible with AIX version 6.1. You can find them in the Archives area of the MySQL web site.
The installer attempts
to repackage the MySQL client shared libraries. The packaging of the
files as they are posted on mysql.com cannot be used by Build Forge.
The user running the installer needs to have write access to the directory
where the client driver files are installed, typically
/opt/mysql.
The installer replaces the files libmsqlclient.a and libmysqlclient.so.15.
If the installer is not able to repackage the files, it notifies you
during installation and continues the installation. In that case,
you must repackage the files manually before running Build Forge. Note: If
you are running other applications that use this MySQL client, you
may want to repackage the files manually in a separate directory.
To manually package the files do the following.
- From the directory MySQL was installed in, create a new directory,
libbf:root@myaix:/opt/mysql/> mkdir libbf - Copy the
lib/libmysqlclient.so.15file into the new directory:root@myaix:/opt/mysql/> cp lib/libmysqlclient.so.15 libbf - Change into the new directory and build the new archive file:
root@myaix:/opt/mysql/> cd libbf root@myaix:/opt/mysql/libbf/> ar -q libmysqlclient.a libmysqlclient.so.15
This directory can now be used as the client library path for the installation process if it has not already run. If one of the silent or command line methods was used, update the LIBPATH in $BFROOT/rc/buildforge to use this path.