MySQL Server and MySQL Connector/C installation packages both provide the files needed to build and run MySQL C API client programs. This section discusses when it is possible to install both products on the same system. For some packaging formats, this is possible without conflict. For others, both products cannot be installed at the same time.
This discussion assumes the use of similar package types for both products (for example, RPM packages for both products). It does not try to describe coexistence between packaging types (for example, use of RPM packages for one product and a tar file package for the other). Nor does it describe coexistence of packages provided by Oracle and those provided by third-party vendors.
If you install both products, it may be necessary to adjust your development tools or runtime environment to choose one set of header files and libraries over the other. See Section 220.127.116.11, “Building C API Client Programs”, and Section 18.104.22.168, “Running C API Client Programs”.
tar and Zip file packages install under the
directory into which you unpack them. For example, you can unpack
MySQL Server and MySQL Connector/C tar packages under
/usr/local and they will unpack into distinct
directory names without conflict.
Windows MSI installers use their own installation directory, so MySQL Server and MySQL Connector/C installers do not conflict.
Mac OS X DMG packages install under the same parent directory but in a different subdirectory, so there is no conflict. For example:
Solaris PKG packages install under the same parent directory but in a different subdirectory, so there is no conflict. For example:
The Solaris MySQL Connector/C installer does not create any symlinks from
system directories such as
/usr/lib into the installation directory.
That must be done manually if desired after installation.
For RPM installations, there are several types of RPM packages.
devel RPM packages are similar to the
corresponding MySQL Connector/C RPM packages. These RPM package types cannot
coexist because the MySQL Server and MySQL Connector/C RPM packages use the
same installation locations for the client library-related files.
This means the following conditions hold:
If MySQL Server
devel RPM packages are installed, they
provide the C API headers and libraries, and there is no need
to install the MySQL Connector/C RPM packages. To install the MySQL Connector/C packages
anyway, you must first remove the corresponding MySQL Server
To install MySQL Server RPM packages if you already have MySQL Connector/C RPM packages installed, you must first remove the MySQL Connector/C RPM packages.
MySQL Server RPM packages other than
devel do not conflict with MySQL Connector/C packages and
can be installed if MySQL Connector/C is installed. This includes the main
server RPM that includes the mysqld server