Skip navigation links
B.4.2.2 Building RPMs »
Section Navigation      [Toggle]

B.4.2.1. Building Static Binaries

Building static binaries is non-trivial under Linux, due to the enormous amount of library dependencies that come from GNOME and associated libraries. Additionally:

  • Many libraries do not come with their static (lib*.a) versions shipped, so we need to build them ourselves.

  • Some libraries can't be linked statically, such as glibc, because of libnss*.so.

  • Some libraries depend on data files and modules from the original package, esp. in case of gtk/gnome. Problems don't just appear when the user don't have these data files installed; things may not work if they use distributions that put data files in different paths.

The current solution is to build a partially static binary, with the most common libraries left dynamically linked (glibc and gtk). gtkmm, gtksourceview, gtkhtml and dependencies (like gnome) are being linked statically. The ideal solution would be to build custom binaries for each major/chosen distribution, but we don't have time/resources for that at the moment.

To build these binaries:

  1. Look at the source/linux/static_make script for all the files that should be removed/moved out of /usr/lib.

  2. Run the script.

That's needed to force the linker to look for the static version of each library and also to explicitly list the dependency libs that were otherwise linked to the dynamic libs.

This is a translation of the MySQL Administrator Manual that can be found at dev.mysql.com. The original MySQL Administrator Manual is in English, and this translation is not necessarily as up to date as the English version. Даний документ є перекладом оригінальної англійської документації по MySQL Administrator яка доступна за адресою dev.mysql.com .