We no longer test builds on OS/2. The notes in this section are provided for your information but may not work on your system.
MySQL uses quite a few open files. Because of this, you should
add something like the following to your
SET EMXOPT=-c -n -h1024
If you do not do this, you may encounter the following error:
xxxx' not found (Errcode: 24)
When using MySQL with OS/2 Warp 3, FixPack 29 or above is required. With OS/2 Warp 4, FixPack 4 or above is required. This is a requirement of the Pthreads library. MySQL must be installed on a partition with a type that supports long file names, such as HPFS, FAT32, and so on.
The INSTALL.CMD script must be run from OS/2's own CMD.EXE and may not work with replacement shells such as 4OS2.EXE.
scripts/mysql-install-db script has
been renamed. It is called
is a REXX script, which sets up the default MySQL security
settings and creates the WorkPlace Shell icons for MySQL.
Dynamic module support is compiled in but not fully tested. Dynamic modules should be compiled using the Pthreads runtime library.
gcc -Zdll -Zmt -Zcrtdll=pthrdrtl -I../include -I../regex -I.. \ -o example udf_example.c -L../lib -lmysqlclient udf_example.def mv example.dll example.udf
Due to limitations in OS/2, UDF module name stems must not
exceed eight characters. Modules are stored in the
/mysql2/udf directory; the
safe-mysqld.cmd script puts this directory
BEGINLIBPATH environment variable.
When using UDF modules, specified extensions are ignored---it
is assumed to be
.udf. For example, in
Unix, the shared module might be named
example.so and you would load a function
from it like this:
CREATE FUNCTION metaphon RETURNS STRING SONAME 'example.so';
In OS/2, the module would be named
example.udf, but you would not specify the
CREATE FUNCTION metaphon RETURNS STRING SONAME 'example';