You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

623 lines
20 KiB

mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
mariadb: improve packaging and configuration At present there are some flaws related to configuration, also related to the packaging of mariadb. For starters there are complaints that the configuration is too static. To address this a new configuration layout is introduced. The primary configuration file (my.cnf) is changed so that it now only includes further configuration files in the directory /etc/mysql/conf.d. More default configuration files are added for the server and the client. This is the new default configuration. With these changes it's possible for the user to select if they want to change the default configuration (in conf.d/*.cnf) or if they want to drop their own files into conf.d instead. If the user .cnf files are read after the default .cnf files (files are included in alphabetical order), they will overwrite the settings from the default configuration. The other flaw is that the my.cnf file is included in mariadb-server. But that doesn't really fit the requirements, as the client also uses the configuration file(s). To accomodate this a new package mariadb-common is added. It installs the shared my.cnf file. The remaining changes add base packages, both for the server and the client. These are meant as foundation for the packages containing the respective binaries. In summary they will install the configuration, small miscellaneous files (SQL scripts etc.) and the user "mariadb". That means that everything is ready for the binaries, like mysql and mysqld. If there is not enough space left on flash memory, the user can just drop the binaries on a pendrive, link them to /usr/bin and get started. The ideas and configuration files were copied from Debian. Some amendments were made. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
6 years ago
  1. #
  2. # Copyright (C) 2018 Sebastian Kemper <sebastian_ml@gmx.net>
  3. #
  4. # This is free software, licensed under the GNU General Public License v2.
  5. # See /LICENSE for more information.
  6. #
  7. include $(TOPDIR)/rules.mk
  8. PKG_NAME:=mariadb
  9. PKG_VERSION:=10.4.13
  10. PKG_RELEASE:=2
  11. PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
  12. PKG_SOURCE_URL := \
  13. https://mirror.netcologne.de/mariadb/$(PKG_NAME)-$(PKG_VERSION)/source \
  14. https://mirror.lstn.net/mariadb/$(PKG_NAME)-$(PKG_VERSION)/source \
  15. https://ftp.yz.yamagata-u.ac.jp/pub/dbms/mariadb/$(PKG_NAME)-$(PKG_VERSION)/source \
  16. https://downloads.mariadb.org/interstitial/$(PKG_NAME)-$(PKG_VERSION)/source
  17. PKG_HASH:=45bbbb12d1de8febd9edf630e940c23cf14efd60570c743b268069516a5d91df
  18. PKG_MAINTAINER:=Michal Hrusecky <Michal@Hrusecky.net>
  19. PKG_LICENSE:=GPL-2.0
  20. PKG_LICENSE_FILES:=COPYING THIRDPARTY
  21. PKG_CPE_ID:=cpe:/a:mariadb:mariadb
  22. HOST_BUILD_PARALLEL:=1
  23. PKG_BUILD_PARALLEL:=1
  24. PKG_USE_MIPS16:=0
  25. HOST_BUILD_DEPENDS:=libxml2/host
  26. # Without libevent2 tests/async_queries sporadically fails on the bots
  27. PKG_BUILD_DEPENDS:=libevent2 mariadb/host
  28. CMAKE_INSTALL:=1
  29. CONF_DIR:=/etc/mysql
  30. PLUGIN_DIR:=/usr/lib/mariadb/plugin
  31. SHARE_DIR:=/usr/share/mariadb
  32. MARIADB_SOCKET=/var/run/mysqld/mysqld.sock
  33. MARIADB_DISABLE_ENGINES := \
  34. cassandra \
  35. example \
  36. mroonga \
  37. oqgraph \
  38. rocksdb \
  39. test_sql_discovery \
  40. tokudb
  41. MARIADB_DISABLE_PLUGINS := \
  42. audit_null \
  43. auth_examples \
  44. aws_key_management \
  45. cracklib_password_check \
  46. daemon_example \
  47. debug_key_management \
  48. example_key_management \
  49. fulltext \
  50. versioning
  51. MARIADB_SERVER_PLUGINS := \
  52. auth_ed25519 \
  53. auth_gssapi \
  54. auth_pam \
  55. auth_pam_v1 \
  56. disks \
  57. feedback \
  58. file_key_management \
  59. ha_archive \
  60. ha_blackhole \
  61. ha_connect \
  62. ha_federated \
  63. ha_federatedx \
  64. ha_sphinx \
  65. ha_spider \
  66. handlersocket \
  67. locales \
  68. metadata_lock_info \
  69. query_cache_info \
  70. query_response_time \
  71. server_audit \
  72. simple_password_check \
  73. sql_errlog \
  74. wsrep_info
  75. PKG_CONFIG_DEPENDS := \
  76. $(patsubst %,CONFIG_PACKAGE_$(PKG_NAME)-server-plugin-%,$(subst _,-,$(MARIADB_SERVER_PLUGINS))) \
  77. CONFIG_PACKAGE_mariadb-server
  78. plugin-auth_ed25519 := PLUGIN_AUTH_ED25519
  79. plugin-auth_gssapi := PLUGIN_AUTH_GSSAPI
  80. plugin-auth_pam := PLUGIN_AUTH_PAM
  81. plugin-auth_pam_v1 := PLUGIN_AUTH_PAM_V1
  82. plugin-disks := PLUGIN_DISKS
  83. plugin-feedback := PLUGIN_FEEDBACK
  84. plugin-file_key_management := PLUGIN_FILE_KEY_MANAGEMENT
  85. plugin-ha_archive := PLUGIN_ARCHIVE
  86. plugin-ha_blackhole := PLUGIN_BLACKHOLE
  87. plugin-ha_connect := PLUGIN_CONNECT
  88. plugin-ha_federated := PLUGIN_FEDERATED
  89. plugin-ha_federatedx := PLUGIN_FEDERATEDX
  90. plugin-ha_sphinx := PLUGIN_SPHINX
  91. plugin-ha_spider := PLUGIN_SPIDER
  92. plugin-handlersocket := PLUGIN_HANDLERSOCKET
  93. plugin-locales := PLUGIN_LOCALES
  94. plugin-metadata_lock_info := PLUGIN_METADATA_LOCK_INFO
  95. plugin-query_cache_info := PLUGIN_QUERY_CACHE_INFO
  96. plugin-query_response_time := PLUGIN_QUERY_RESPONSE_TIME
  97. plugin-server_audit := PLUGIN_SERVER_AUDIT
  98. plugin-simple_password_check := PLUGIN_SIMPLE_PASSWORD_CHECK
  99. plugin-sql_errlog := PLUGIN_SQL_ERRLOG
  100. plugin-wsrep_info := PLUGIN_WSREP_INFO
  101. MARIADB_CLIENT := \
  102. mysql \
  103. mysqlcheck
  104. MARIADB_CLIENT_EXTRA := \
  105. msql2mysql \
  106. mysql_find_rows \
  107. mysql_plugin \
  108. mysql_waitpid \
  109. mysqlaccess \
  110. mysqlbinlog \
  111. mysqldump \
  112. mysqlimport \
  113. mysqlshow \
  114. mysqlslap \
  115. mytop
  116. MARIADB_SERVER := \
  117. innochecksum \
  118. my_print_defaults \
  119. mysql_install_db \
  120. mysql_upgrade \
  121. mysqladmin \
  122. mysqld \
  123. mysqld_safe
  124. MARIADB_SERVER_EXTRA := \
  125. aria_chk \
  126. aria_dump_log \
  127. aria_ftdump \
  128. aria_pack \
  129. aria_read_log \
  130. mariabackup \
  131. myisam_ftdump \
  132. myisamchk \
  133. myisamlog \
  134. myisampack \
  135. mysql_convert_table_format \
  136. mysql_fix_extensions \
  137. mysql_secure_installation \
  138. mysql_setpermission \
  139. mysql_tzinfo_to_sql \
  140. mysqld_multi \
  141. mysqld_safe_helper \
  142. mysqldumpslow \
  143. mysqlhotcopy \
  144. perror \
  145. replace \
  146. resolve_stack_dump \
  147. wsrep_sst_mariabackup \
  148. wsrep_sst_mysqldump \
  149. wsrep_sst_rsync \
  150. wsrep_sst_rsync_wan
  151. include $(INCLUDE_DIR)/package.mk
  152. include $(INCLUDE_DIR)/host-build.mk
  153. include $(INCLUDE_DIR)/cmake.mk
  154. include $(INCLUDE_DIR)/nls.mk
  155. MARIADB_COMMON_DEPENDS := \
  156. $(ICONV_DEPENDS) \
  157. +libatomic \
  158. +libopenssl \
  159. +libstdcpp \
  160. +zlib \
  161. @!USE_UCLIBC
  162. # Pass CPPFLAGS in the CFLAGS as otherwise the build system will
  163. # ignore them.
  164. TARGET_CFLAGS+=$(TARGET_CPPFLAGS)
  165. define Package/mariadb/disable/engine
  166. echo > $(1)/storage/$(2)/CMakeLists.txt
  167. endef
  168. define Package/mariadb/disable/plugin
  169. echo > $(1)/plugin/$(2)/CMakeLists.txt
  170. endef
  171. define Package/mariadb/install/bin
  172. $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/$(2) $(1)/usr/bin
  173. cd "$(PKG_INSTALL_DIR)/usr/bin"; find . -maxdepth 1 -type l \
  174. -regex './$(subst mysql,mariadb[-]*,$(subst _,-,$(2)))' \
  175. | xargs -I{} $(CP) {} "$(1)/usr/bin"
  176. endef
  177. define Package/mariadb/install/plugin
  178. $(INSTALL_BIN) $(PKG_INSTALL_DIR)$(PLUGIN_DIR)/$(2).so $(1)$(PLUGIN_DIR)
  179. endef
  180. define Package/mariadb/description/Default
  181. MariaDB is a very fast and robust SQL database server.
  182. endef
  183. define Package/mariadb/Default
  184. SECTION:=utils
  185. CATEGORY:=Utilities
  186. URL:=https://mariadb.org/
  187. SUBMENU:=Database
  188. endef
  189. define Package/mariadb-client
  190. $(call Package/mariadb/Default)
  191. TITLE:=MariaDB database client
  192. MENU:=1
  193. DEPENDS:=mariadb-client-base
  194. endef
  195. define Package/mariadb-client/description
  196. $(call Package/mariadb/description/Default)
  197. This package includes the following core client binaries:
  198. $(subst $(space),$(newline),$(MARIADB_CLIENT))
  199. endef
  200. define Package/mariadb-client-base
  201. $(call Package/mariadb/Default)
  202. TITLE:=MariaDB database client base
  203. DEPENDS:=mariadb-common \
  204. $(MARIADB_COMMON_DEPENDS) \
  205. +libedit
  206. endef
  207. define Package/mariadb-client-base/conffiles
  208. $(CONF_DIR)/conf.d/50-mysql-clients.cnf
  209. endef
  210. define Package/mariadb-client-base/description
  211. $(call Package/mariadb/description/Default)
  212. This package provides the foundation for mariadb-client. It installs the
  213. configuration and the dependencies.
  214. endef
  215. define Package/mariadb-client-extra
  216. $(call Package/mariadb/Default)
  217. TITLE:=MariaDB database client extra
  218. DEPENDS:=mariadb-client
  219. endef
  220. define Package/mariadb-client-extra/description
  221. $(call Package/mariadb/description/Default)
  222. This package includes the following extra client binaries:
  223. $(subst $(space),$(newline),$(MARIADB_CLIENT_EXTRA))
  224. endef
  225. define Package/mariadb-server
  226. $(call Package/mariadb/Default)
  227. DEPENDS:=mariadb-server-base
  228. TITLE:=MariaDB database server
  229. MENU:=1
  230. PROVIDES:=mysql-server
  231. endef
  232. define Package/mariadb-server/conffiles
  233. /usr/bin/mysqld_safe
  234. endef
  235. define Package/mariadb-server/description
  236. $(call Package/mariadb/description/Default)
  237. This package includes the following core server binaries:
  238. $(subst $(space),$(newline),$(MARIADB_SERVER))
  239. endef
  240. define Package/mariadb-server-base
  241. $(call Package/mariadb/Default)
  242. DEPENDS:=mariadb-common \
  243. $(MARIADB_COMMON_DEPENDS) \
  244. +libaio \
  245. +liblzma \
  246. +libpcre \
  247. +resolveip
  248. TITLE:=MariaDB database server base
  249. USERID:=mariadb=376:mariadb=376
  250. endef
  251. define Package/mariadb-server-base/conffiles
  252. $(CONF_DIR)/conf.d/50-server.cnf
  253. $(CONF_DIR)/conf.d/60-galera.cnf
  254. /etc/config/mysqld
  255. endef
  256. define Package/mariadb-server-base/description
  257. $(call Package/mariadb/description/Default)
  258. This package provides the foundation for mariadb-server. It installs the
  259. init script, support files (configuration etc.), the user "mariadb" and
  260. the dependencies.
  261. endef
  262. define Package/mariadb-server-extra
  263. $(call Package/mariadb/Default)
  264. TITLE:=MariaDB database server extra
  265. DEPENDS:=mariadb-server
  266. endef
  267. define Package/mariadb-server-extra/description
  268. $(call Package/mariadb/description/Default)
  269. This package includes the following extra server binaries:
  270. $(subst $(space),$(newline),$(MARIADB_SERVER_EXTRA))
  271. endef
  272. # We won't need unit tests
  273. CMAKE_OPTIONS += -DWITH_UNIT_TESTS=0
  274. # This value is determined automatically during straight compile by compiling
  275. # and running a test code. You cannot do that during cross-compile. However the
  276. # stack grows downward in most if not all modern systems. The only exception
  277. # according to buildroot is PA-RISC which is not supported by OpenWrt as far as
  278. # I know. Therefore it makes sense to hardcode the value. If an arch is added
  279. # the stack of which grows up one should expect unpredictable behavior at run
  280. # time.
  281. CMAKE_OPTIONS += -DSTACK_DIRECTION=-1
  282. # Make it explicit that we are cross-compiling
  283. CMAKE_OPTIONS += -DCMAKE_CROSSCOMPILING=1
  284. # Explicitly disable dtrace to avoid detection of a host version
  285. CMAKE_OPTIONS += -DENABLE_DTRACE=0
  286. # Prevent MariaDB from messing with OpenWrt's C(XX)FLAGS
  287. CMAKE_OPTIONS += -DSECURITY_HARDENED=OFF
  288. ifeq ($(CONFIG_PACKAGE_mariadb-server),)
  289. CMAKE_OPTIONS += -DWITHOUT_SERVER=ON
  290. else
  291. # Enable the auth_socket plugin and let unix user root access MariaDB without a
  292. # separate password.
  293. CMAKE_OPTIONS += -DWITHOUT_SERVER=OFF -DPLUGIN_AUTH_SOCKET=STATIC
  294. endif
  295. CMAKE_OPTIONS += \
  296. -DCONNECT_WITH_JDBC=NO \
  297. -DCONNECT_WITH_LIBXML2=system \
  298. -DCONNECT_WITH_MONGO=NO \
  299. -DCONNECT_WITH_ODBC=NO \
  300. -DDISABLE_SHARED=NO \
  301. -DENABLED_PROFILING=OFF \
  302. -DENABLE_STATIC_LIBS=OFF \
  303. -DINSTALL_DOCDIR=share/doc/mariadb \
  304. -DINSTALL_DOCREADMEDIR=share/doc/mariadb \
  305. -DINSTALL_INFODIR=share/info \
  306. -DINSTALL_MANDIR=share/man \
  307. -DINSTALL_MYSQLSHAREDIR=share/mariadb \
  308. -DINSTALL_MYSQLTESTDIR="" \
  309. -DINSTALL_PAMDATADIR="/etc/security" \
  310. -DINSTALL_PAMDIR="/lib/security" \
  311. -DINSTALL_PLUGINDIR=lib/mariadb/plugin \
  312. -DINSTALL_SBINDIR=bin \
  313. -DINSTALL_SCRIPTDIR=bin \
  314. -DINSTALL_SQLBENCHDIR="" \
  315. -DINSTALL_SUPPORTFILESDIR=share/mariadb \
  316. -DINSTALL_UNIX_ADDRDIR=$(MARIADB_SOCKET) \
  317. -DMYSQL_DATADIR=/var/lib/mysql \
  318. -DMYSQL_UNIX_ADDR=$(MARIADB_SOCKET) \
  319. -DSKIP_TESTS=ON \
  320. -DWITH_DEBUG=OFF \
  321. -DWITH_EMBEDDED_SERVER=OFF \
  322. -DWITH_INNODB_BZIP2=OFF \
  323. -DWITH_INNODB_LZ4=OFF \
  324. -DWITH_INNODB_LZMA=ON \
  325. -DWITH_INNODB_LZO=OFF \
  326. -DWITH_INNODB_SNAPPY=OFF \
  327. -DWITH_JEMALLOC=OFF \
  328. -DWITH_LIBARCHIVE=OFF \
  329. -DWITH_LIBWRAP=OFF \
  330. -DWITH_MARIABACKUP=ON \
  331. -DWITH_NUMA=OFF \
  332. -DWITH_PCRE=system \
  333. -DWITH_SAFEMALLOC=OFF \
  334. -DWITH_SSL=system \
  335. -DWITH_SYSTEMD=no \
  336. -DWITH_VALGRIND=OFF \
  337. -DWITH_ZLIB=system
  338. # Help MariaDB find the correct libiconv.
  339. # nls.mk sets it up so that with CONFIG_BUILD_NLS libiconv-full would be used,
  340. # otherwise libiconv-stub (independent of the selected libc). MariaDB needs a
  341. # leg up to find/pick the right lib.
  342. CMAKE_OPTIONS += \
  343. -DICONV_INCLUDE_DIR=$(ICONV_PREFIX)/include \
  344. -DICONV_LIBRARIES=$(ICONV_PREFIX)/lib/libiconv.$(if $(CONFIG_BUILD_NLS),so,a)
  345. CMAKE_OPTIONS += \
  346. $(foreach p,$(MARIADB_SERVER_PLUGINS),-D$(plugin-$(p))=$(if $(CONFIG_PACKAGE_$(PKG_NAME)-server-plugin-$(subst _,-,$(p))),DYNAMIC,NO))
  347. # Disable some client library plugins
  348. CMAKE_OPTIONS += \
  349. -DCLIENT_PLUGIN_AUTH_GSSAPI_CLIENT=OFF \
  350. -DCLIENT_PLUGIN_REMOTE_IO=OFF
  351. # Set CMAKE_FIND_ROOT_PATH_MODE_INCLUDE and CMAKE_FIND_ROOT_PATH_MODE_LIBRARY
  352. # to BOTH as otherwise the host build will not find some required dependencies
  353. # installed on the host machine, like ncurses.
  354. #
  355. # Add "$(STAGING_DIR_HOSTPKG)/lib" to the RPATH of the host helpers,
  356. # otherwise they might not find the location of a library at run time.
  357. CMAKE_HOST_OPTIONS += \
  358. -DCMAKE_BUILD_WITH_INSTALL_RPATH=TRUE \
  359. -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=BOTH \
  360. -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=BOTH \
  361. -DCMAKE_INSTALL_RPATH="$(STAGING_DIR_HOSTPKG)/lib" \
  362. -DCMAKE_SKIP_RPATH=FALSE \
  363. -DWITHOUT_SERVER=OFF
  364. # Some helpers must be compiled for host in order to crosscompile MariaDB for
  365. # the target. They are then included by import_executables.cmake which is
  366. # generated during the build of the host helpers. It is not necessary to build
  367. # the whole host package, only the "import_executables" target.
  368. # -DIMPORT_EXECUTABLES=$(HOST_BUILD_DIR)/import_executables.cmake
  369. # must then be passed to cmake during target build.
  370. # See also https://mariadb.com/kb/en/mariadb/cross-compiling-mariadb/
  371. CMAKE_OPTIONS += -DIMPORT_EXECUTABLES=$(STAGING_DIR_HOSTPKG)/share/mariadb/import_executables.cmake
  372. # Disable some engines/plugins here as well - decreases the number of cmake checks.
  373. define Host/Prepare
  374. $(call Host/Prepare/Default)
  375. $(foreach e,$(MARIADB_DISABLE_ENGINES),$(call Package/mariadb/disable/engine,$(HOST_BUILD_DIR),$(e));)
  376. $(foreach p,$(MARIADB_DISABLE_PLUGINS),$(call Package/mariadb/disable/plugin,$(HOST_BUILD_DIR),$(p));)
  377. endef
  378. define Host/Compile
  379. $(call Host/Compile/Default,import_executables)
  380. endef
  381. define Host/Install
  382. $(SED) 's|$(HOST_BUILD_DIR)|$(STAGING_DIR_HOSTPKG)/share/mariadb|' $(HOST_BUILD_DIR)/import_executables.cmake
  383. $(INSTALL_DIR) $(1)/share/mariadb/{dbug,extra,scripts,sql}
  384. $(INSTALL_BIN) $(HOST_BUILD_DIR)/dbug/factorial $(1)/share/mariadb/dbug
  385. $(INSTALL_BIN) $(HOST_BUILD_DIR)/extra/comp_err $(1)/share/mariadb/extra
  386. $(INSTALL_BIN) $(HOST_BUILD_DIR)/scripts/comp_sql $(1)/share/mariadb/scripts
  387. $(INSTALL_BIN) $(HOST_BUILD_DIR)/sql/{gen_lex_hash,gen_lex_token} $(1)/share/mariadb/sql
  388. $(INSTALL_DATA) $(HOST_BUILD_DIR)/import_executables.cmake $(1)/share/mariadb
  389. endef
  390. # LIBICONV_PLUG is used in GNU's libiconv for redefinition of exports [e.g.
  391. # from libiconv_open() to iconv_open()]. But in OpenWrt this variable is not set
  392. # when building libiconv-full. So when MariaDB sets LIBICONV_PLUG it expects
  393. # iconv_open() to be available for example, which is not the case - only
  394. # libiconv_open() is. To address this prevent the variable from being set.
  395. # libiconv-stub does not use this variable, so there is no harm in always doing
  396. # this.
  397. define Build/Prepare
  398. $(call Build/Prepare/Default)
  399. $(SED) '/ADD_DEFINITIONS(-DLIBICONV_PLUG)/d' $(PKG_BUILD_DIR)/libmariadb/libmariadb/CMakeLists.txt
  400. $(foreach e,$(MARIADB_DISABLE_ENGINES),$(call Package/mariadb/disable/engine,$(PKG_BUILD_DIR),$(e));)
  401. $(foreach p,$(MARIADB_DISABLE_PLUGINS),$(call Package/mariadb/disable/plugin,$(PKG_BUILD_DIR),$(p));)
  402. endef
  403. # Define Build/InstallDev, otherwise build system starts installing files into
  404. # staging area, which would interfere with mariadb-connector-c.
  405. define Build/InstallDev
  406. endef
  407. define Package/mariadb-client/install
  408. $(INSTALL_DIR) $(1)/usr/bin
  409. $(foreach b,$(MARIADB_CLIENT),$(call Package/mariadb/install/bin,$(1),$(b));)
  410. # Install convenience links for mysqlcheck multi-call binary
  411. cd $(1)/usr/bin; $(LN) mysqlcheck mysqlanalyze
  412. cd $(1)/usr/bin; $(LN) mysqlcheck mysqlrepair
  413. cd $(1)/usr/bin; $(LN) mysqlcheck mysqloptimize
  414. endef
  415. define Package/mariadb-client-base/install
  416. $(INSTALL_DIR) $(1)$(CONF_DIR)/conf.d
  417. $(INSTALL_DATA) conf/50-mysql-clients.cnf $(1)$(CONF_DIR)/conf.d
  418. endef
  419. define Package/mariadb-client-extra/install
  420. $(INSTALL_DIR) $(1)/usr/bin
  421. $(foreach b,$(MARIADB_CLIENT_EXTRA),$(call Package/mariadb/install/bin,$(1),$(b));)
  422. endef
  423. define Package/mariadb-server/install
  424. $(INSTALL_DIR) $(1)/usr/bin
  425. $(foreach b,$(MARIADB_SERVER),$(call Package/mariadb/install/bin,$(1),$(b));)
  426. endef
  427. define Package/mariadb-server-base/install
  428. $(INSTALL_DIR) $(1)$(CONF_DIR)/conf.d
  429. $(INSTALL_DIR) $(1)$(SHARE_DIR)/charsets
  430. $(INSTALL_DIR) $(1)$(SHARE_DIR)/english
  431. $(INSTALL_DIR) $(1)/etc/config
  432. $(INSTALL_DIR) $(1)/etc/init.d
  433. $(INSTALL_BIN) files/mysqld.init $(1)/etc/init.d/mysqld
  434. $(SED) '/^[a-z]/s/^/#/' $(PKG_INSTALL_DIR)$(SHARE_DIR)/wsrep.cnf
  435. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/wsrep.cnf $(1)$(CONF_DIR)/conf.d/60-galera.cnf
  436. $(INSTALL_DATA) conf/50-server.cnf $(1)$(CONF_DIR)/conf.d
  437. $(INSTALL_CONF) files/mysqld.config $(1)/etc/config/mysqld
  438. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/charsets/* $(1)$(SHARE_DIR)/charsets
  439. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/english/errmsg.sys $(1)$(SHARE_DIR)/english
  440. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/fill_help_tables.sql $(1)$(SHARE_DIR)
  441. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/maria_add_gis_sp_bootstrap.sql $(1)$(SHARE_DIR)
  442. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_performance_tables.sql $(1)$(SHARE_DIR)
  443. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_system_tables.sql $(1)$(SHARE_DIR)
  444. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_system_tables_data.sql $(1)$(SHARE_DIR)
  445. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_test_db.sql $(1)$(SHARE_DIR)
  446. endef
  447. define Package/mariadb-server-extra/install
  448. $(INSTALL_DIR) $(1)/usr/bin
  449. $(INSTALL_DATA) $(PKG_INSTALL_DIR)/usr/bin/wsrep_sst_common $(1)/usr/bin
  450. $(SED) 's,/bin/bash,/bin/sh,g' $(PKG_INSTALL_DIR)/usr/bin/wsrep_sst_*
  451. $(foreach b,$(MARIADB_SERVER_EXTRA),$(call Package/mariadb/install/bin,$(1),$(b));)
  452. cd $(1)/usr/bin; $(LN) mariabackup mariadb-backup
  453. endef
  454. define BuildPlugin
  455. define Package/mariadb-server-plugin-$(subst _,-,$(1))
  456. $(call Package/mariadb/Default)
  457. TITLE:=mariadb-server plugin
  458. DEPENDS:=mariadb-server $(patsubst +%,+PACKAGE_mariadb-server-plugin-$(subst _,-,$(1)):%,$(2))
  459. endef
  460. define Package/mariadb-server-plugin-$(subst _,-,$(1))/description
  461. $(call Package/mariadb/description/Default)
  462. This package provides the $(1) plugin.
  463. endef
  464. define Package/mariadb-server-plugin-$(subst _,-,$(1))/install
  465. $(INSTALL_DIR) $$(1)$(PLUGIN_DIR)
  466. $(call Package/mariadb/install/plugin,$$(1),$(1))
  467. ifeq ($(1),auth_pam)
  468. $(INSTALL_DIR) -m0750 $$(1)$(PLUGIN_DIR)/auth_pam_tool_dir
  469. $(INSTALL_SUID) \
  470. $(PKG_INSTALL_DIR)$(PLUGIN_DIR)/auth_pam_tool_dir/auth_pam_tool \
  471. $$(1)$(PLUGIN_DIR)/auth_pam_tool_dir
  472. $(INSTALL_DIR) $$(1)/etc/security
  473. $(INSTALL_DATA) \
  474. $(PKG_INSTALL_DIR)/etc/security/user_map.conf \
  475. $$(1)/etc/security
  476. $(INSTALL_DIR) $$(1)/lib/security
  477. $(INSTALL_DATA) \
  478. $(PKG_INSTALL_DIR)/lib/security/pam_user_map.so \
  479. $$(1)/lib/security
  480. endif
  481. ifeq ($(1),ha_spider)
  482. $(INSTALL_DIR) $$(1)$(SHARE_DIR)
  483. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/install_spider.sql \
  484. $$(1)$(SHARE_DIR)
  485. endif
  486. endef
  487. $$(eval $$(call BuildPackage,mariadb-server-plugin-$(subst _,-,$(1))))
  488. endef
  489. # Directory "auth_pam_tool_dir" is installed with '-m0750' above and
  490. # contains SUID binary "auth_pam_tool". Below post-install script
  491. # changes the group of "auth_pam_tool_dir" to mariadb, so user mariadb
  492. # can access the folder (and the SUID binary). The script only changes
  493. # the group if the directory is currently owned by "root:root".
  494. define Package/mariadb-server-plugin-auth-pam/postinst
  495. #!/bin/sh
  496. if [ -z "$${IPKG_INSTROOT}" ]; then
  497. dir="/usr/lib/mariadb/plugin/auth_pam_tool_dir"
  498. if ! [ -L "$$dir" ] && [ -d "$$dir" ] && [ -O "$$dir" ] && [ -G "$$dir" ]; then
  499. chown :mariadb "$$dir"
  500. fi
  501. fi
  502. exit 0
  503. endef
  504. $(eval $(call HostBuild))
  505. $(eval $(call BuildPackage,mariadb-client))
  506. $(eval $(call BuildPackage,mariadb-client-base))
  507. $(eval $(call BuildPackage,mariadb-client-extra))
  508. $(eval $(call BuildPackage,mariadb-server))
  509. $(eval $(call BuildPackage,mariadb-server-base))
  510. $(eval $(call BuildPackage,mariadb-server-extra))
  511. $(eval $(call BuildPlugin,auth_ed25519,))
  512. $(eval $(call BuildPlugin,auth_gssapi,+krb5-libs))
  513. $(eval $(call BuildPlugin,auth_pam,+libpam))
  514. $(eval $(call BuildPlugin,auth_pam_v1,+libpam))
  515. $(eval $(call BuildPlugin,disks,))
  516. $(eval $(call BuildPlugin,feedback,))
  517. $(eval $(call BuildPlugin,file_key_management,))
  518. $(eval $(call BuildPlugin,ha_archive,))
  519. $(eval $(call BuildPlugin,ha_blackhole,))
  520. $(eval $(call BuildPlugin,ha_connect,+libxml2))
  521. $(eval $(call BuildPlugin,ha_federated,))
  522. $(eval $(call BuildPlugin,ha_federatedx,))
  523. $(eval $(call BuildPlugin,ha_sphinx,))
  524. $(eval $(call BuildPlugin,ha_spider,))
  525. $(eval $(call BuildPlugin,handlersocket,))
  526. $(eval $(call BuildPlugin,locales,))
  527. $(eval $(call BuildPlugin,metadata_lock_info,))
  528. $(eval $(call BuildPlugin,query_cache_info,))
  529. $(eval $(call BuildPlugin,query_response_time,))
  530. $(eval $(call BuildPlugin,server_audit,))
  531. $(eval $(call BuildPlugin,simple_password_check,))
  532. $(eval $(call BuildPlugin,sql_errlog,))
  533. $(eval $(call BuildPlugin,wsrep_info,))