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.

605 lines
19 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.18
  10. PKG_RELEASE:=1
  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:=330d9e8273002fc92f0f3f3f9b08157a3cab1265a0f114adeb6235e4283a0d3e
  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. CONF_DIR:=/etc/mysql
  29. PLUGIN_DIR:=/usr/lib/mariadb/plugin
  30. SHARE_DIR:=/usr/share/mariadb
  31. MARIADB_SOCKET=/var/run/mysqld/mysqld.sock
  32. MARIADB_DISABLE_ENGINES := \
  33. cassandra \
  34. example \
  35. mroonga \
  36. oqgraph \
  37. rocksdb \
  38. test_sql_discovery \
  39. tokudb
  40. MARIADB_DISABLE_PLUGINS := \
  41. audit_null \
  42. auth_examples \
  43. aws_key_management \
  44. cracklib_password_check \
  45. daemon_example \
  46. debug_key_management \
  47. example_key_management \
  48. fulltext \
  49. versioning
  50. MARIADB_SERVER_PLUGINS := \
  51. auth_ed25519 \
  52. auth_gssapi \
  53. auth_pam \
  54. auth_pam_v1 \
  55. disks \
  56. feedback \
  57. file_key_management \
  58. ha_archive \
  59. ha_blackhole \
  60. ha_connect \
  61. ha_federated \
  62. ha_federatedx \
  63. ha_sphinx \
  64. ha_spider \
  65. handlersocket \
  66. locales \
  67. metadata_lock_info \
  68. query_cache_info \
  69. query_response_time \
  70. server_audit \
  71. simple_password_check \
  72. sql_errlog \
  73. wsrep_info
  74. PKG_CONFIG_DEPENDS := \
  75. $(patsubst %,CONFIG_PACKAGE_$(PKG_NAME)-server-plugin-%,$(subst _,-,$(MARIADB_SERVER_PLUGINS))) \
  76. CONFIG_PACKAGE_mariadb-server
  77. plugin-auth_ed25519 := PLUGIN_AUTH_ED25519
  78. plugin-auth_gssapi := PLUGIN_AUTH_GSSAPI
  79. plugin-auth_pam := PLUGIN_AUTH_PAM
  80. plugin-auth_pam_v1 := PLUGIN_AUTH_PAM_V1
  81. plugin-disks := PLUGIN_DISKS
  82. plugin-feedback := PLUGIN_FEEDBACK
  83. plugin-file_key_management := PLUGIN_FILE_KEY_MANAGEMENT
  84. plugin-ha_archive := PLUGIN_ARCHIVE
  85. plugin-ha_blackhole := PLUGIN_BLACKHOLE
  86. plugin-ha_connect := PLUGIN_CONNECT
  87. plugin-ha_federated := PLUGIN_FEDERATED
  88. plugin-ha_federatedx := PLUGIN_FEDERATEDX
  89. plugin-ha_sphinx := PLUGIN_SPHINX
  90. plugin-ha_spider := PLUGIN_SPIDER
  91. plugin-handlersocket := PLUGIN_HANDLERSOCKET
  92. plugin-locales := PLUGIN_LOCALES
  93. plugin-metadata_lock_info := PLUGIN_METADATA_LOCK_INFO
  94. plugin-query_cache_info := PLUGIN_QUERY_CACHE_INFO
  95. plugin-query_response_time := PLUGIN_QUERY_RESPONSE_TIME
  96. plugin-server_audit := PLUGIN_SERVER_AUDIT
  97. plugin-simple_password_check := PLUGIN_SIMPLE_PASSWORD_CHECK
  98. plugin-sql_errlog := PLUGIN_SQL_ERRLOG
  99. plugin-wsrep_info := PLUGIN_WSREP_INFO
  100. MARIADB_CLIENT := \
  101. mysql \
  102. mysqlcheck
  103. MARIADB_CLIENT_EXTRA := \
  104. msql2mysql \
  105. mysql_find_rows \
  106. mysql_plugin \
  107. mysql_waitpid \
  108. mysqlaccess \
  109. mysqlbinlog \
  110. mysqldump \
  111. mysqlimport \
  112. mysqlshow \
  113. mysqlslap \
  114. mytop
  115. MARIADB_SERVER := \
  116. innochecksum \
  117. my_print_defaults \
  118. mysql_install_db \
  119. mysql_upgrade \
  120. mysqladmin \
  121. mysqld
  122. MARIADB_SERVER_EXTRA := \
  123. aria_chk \
  124. aria_dump_log \
  125. aria_ftdump \
  126. aria_pack \
  127. aria_read_log \
  128. mariabackup \
  129. myisam_ftdump \
  130. myisamchk \
  131. myisamlog \
  132. myisampack \
  133. mysql_convert_table_format \
  134. mysql_fix_extensions \
  135. mysql_secure_installation \
  136. mysql_setpermission \
  137. mysql_tzinfo_to_sql \
  138. mysqld_multi \
  139. mysqld_safe \
  140. mysqld_safe_helper \
  141. mysqldumpslow \
  142. mysqlhotcopy \
  143. perror \
  144. replace \
  145. resolve_stack_dump \
  146. wsrep_sst_mariabackup \
  147. wsrep_sst_mysqldump \
  148. wsrep_sst_rsync \
  149. wsrep_sst_rsync_wan
  150. include $(INCLUDE_DIR)/package.mk
  151. include $(INCLUDE_DIR)/host-build.mk
  152. include $(INCLUDE_DIR)/cmake.mk
  153. include $(INCLUDE_DIR)/nls.mk
  154. MARIADB_COMMON_DEPENDS := \
  155. $(ICONV_DEPENDS) \
  156. +libatomic \
  157. +libopenssl \
  158. +libstdcpp \
  159. +zlib
  160. # Pass CPPFLAGS in the CFLAGS as otherwise the build system will
  161. # ignore them.
  162. TARGET_CFLAGS+=$(TARGET_CPPFLAGS)
  163. define Package/mariadb/disable/engine
  164. echo > $(1)/storage/$(2)/CMakeLists.txt
  165. endef
  166. define Package/mariadb/disable/plugin
  167. echo > $(1)/plugin/$(2)/CMakeLists.txt
  168. endef
  169. define Package/mariadb/install/bin
  170. $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/$(2) $(1)/usr/bin
  171. cd "$(PKG_INSTALL_DIR)/usr/bin"; find . -maxdepth 1 -type l \
  172. -regex './$(subst mysql,mariadb[-]*,$(subst _,-,$(2)))' \
  173. | xargs -I{} $(CP) {} "$(1)/usr/bin"
  174. endef
  175. define Package/mariadb/install/plugin
  176. $(INSTALL_BIN) $(PKG_INSTALL_DIR)$(PLUGIN_DIR)/$(2).so $(1)$(PLUGIN_DIR)
  177. endef
  178. define Package/mariadb/description/Default
  179. MariaDB is a very fast and robust SQL database server.
  180. endef
  181. define Package/mariadb/Default
  182. SECTION:=utils
  183. CATEGORY:=Utilities
  184. URL:=https://mariadb.org/
  185. SUBMENU:=Database
  186. endef
  187. define Package/mariadb-client
  188. $(call Package/mariadb/Default)
  189. TITLE:=MariaDB database client
  190. MENU:=1
  191. DEPENDS:=mariadb-client-base
  192. endef
  193. define Package/mariadb-client/description
  194. $(call Package/mariadb/description/Default)
  195. This package includes the following core client binaries:
  196. $(subst $(space),$(newline),$(MARIADB_CLIENT))
  197. endef
  198. define Package/mariadb-client-base
  199. $(call Package/mariadb/Default)
  200. TITLE:=MariaDB database client base
  201. DEPENDS:=mariadb-common \
  202. $(MARIADB_COMMON_DEPENDS) \
  203. +libedit
  204. endef
  205. define Package/mariadb-client-base/conffiles
  206. $(CONF_DIR)/conf.d/50-mysql-clients.cnf
  207. endef
  208. define Package/mariadb-client-base/description
  209. $(call Package/mariadb/description/Default)
  210. This package provides the foundation for mariadb-client. It installs the
  211. configuration and the dependencies.
  212. endef
  213. define Package/mariadb-client-extra
  214. $(call Package/mariadb/Default)
  215. TITLE:=MariaDB database client extra
  216. DEPENDS:=mariadb-client
  217. endef
  218. define Package/mariadb-client-extra/description
  219. $(call Package/mariadb/description/Default)
  220. This package includes the following extra client binaries:
  221. $(subst $(space),$(newline),$(MARIADB_CLIENT_EXTRA))
  222. endef
  223. define Package/mariadb-server
  224. $(call Package/mariadb/Default)
  225. DEPENDS:=mariadb-server-base
  226. TITLE:=MariaDB database server
  227. MENU:=1
  228. PROVIDES:=mysql-server
  229. endef
  230. define Package/mariadb-server/conffiles
  231. /usr/bin/mysqld_safe
  232. endef
  233. define Package/mariadb-server/description
  234. $(call Package/mariadb/description/Default)
  235. This package includes the following core server binaries:
  236. $(subst $(space),$(newline),$(MARIADB_SERVER))
  237. endef
  238. define Package/mariadb-server-base
  239. $(call Package/mariadb/Default)
  240. DEPENDS:=mariadb-common \
  241. $(MARIADB_COMMON_DEPENDS) \
  242. +libaio \
  243. +liblzma \
  244. +libpcre \
  245. +resolveip
  246. TITLE:=MariaDB database server base
  247. USERID:=mariadb=376:mariadb=376
  248. endef
  249. define Package/mariadb-server-base/conffiles
  250. $(CONF_DIR)/conf.d/50-server.cnf
  251. $(CONF_DIR)/conf.d/60-galera.cnf
  252. /etc/config/mysqld
  253. endef
  254. define Package/mariadb-server-base/description
  255. $(call Package/mariadb/description/Default)
  256. This package provides the foundation for mariadb-server. It installs the
  257. init script, support files (configuration etc.), the user "mariadb" and
  258. the dependencies.
  259. endef
  260. define Package/mariadb-server-extra
  261. $(call Package/mariadb/Default)
  262. TITLE:=MariaDB database server extra
  263. DEPENDS:=mariadb-server
  264. endef
  265. define Package/mariadb-server-extra/description
  266. $(call Package/mariadb/description/Default)
  267. This package includes the following extra server binaries:
  268. $(subst $(space),$(newline),$(MARIADB_SERVER_EXTRA))
  269. endef
  270. # We won't need unit tests
  271. CMAKE_OPTIONS += -DWITH_UNIT_TESTS=0
  272. # This value is determined automatically during straight compile by compiling
  273. # and running a test code. You cannot do that during cross-compile. However the
  274. # stack grows downward in most if not all modern systems. The only exception
  275. # according to buildroot is PA-RISC which is not supported by OpenWrt as far as
  276. # I know. Therefore it makes sense to hardcode the value. If an arch is added
  277. # the stack of which grows up one should expect unpredictable behavior at run
  278. # time.
  279. CMAKE_OPTIONS += -DSTACK_DIRECTION=-1
  280. # Make it explicit that we are cross-compiling
  281. CMAKE_OPTIONS += -DCMAKE_CROSSCOMPILING=1
  282. # Explicitly disable dtrace to avoid detection of a host version
  283. CMAKE_OPTIONS += -DENABLE_DTRACE=0
  284. # Prevent MariaDB from messing with OpenWrt's C(XX)FLAGS
  285. CMAKE_OPTIONS += -DSECURITY_HARDENED=OFF
  286. ifeq ($(CONFIG_PACKAGE_mariadb-server),)
  287. CMAKE_OPTIONS += -DWITHOUT_SERVER=ON
  288. else
  289. # Enable the auth_socket plugin and let unix user root access MariaDB without a
  290. # separate password.
  291. CMAKE_OPTIONS += -DWITHOUT_SERVER=OFF -DPLUGIN_AUTH_SOCKET=STATIC
  292. endif
  293. CMAKE_OPTIONS += \
  294. -DCONNECT_WITH_JDBC=NO \
  295. -DCONNECT_WITH_LIBXML2=system \
  296. -DCONNECT_WITH_MONGO=NO \
  297. -DCONNECT_WITH_ODBC=NO \
  298. -DDISABLE_SHARED=NO \
  299. -DENABLED_PROFILING=OFF \
  300. -DENABLE_STATIC_LIBS=OFF \
  301. -DINSTALL_DOCDIR=share/doc/mariadb \
  302. -DINSTALL_DOCREADMEDIR=share/doc/mariadb \
  303. -DINSTALL_INFODIR=share/info \
  304. -DINSTALL_MANDIR=share/man \
  305. -DINSTALL_MYSQLSHAREDIR=share/mariadb \
  306. -DINSTALL_MYSQLTESTDIR="" \
  307. -DINSTALL_PAMDATADIR="/etc/security" \
  308. -DINSTALL_PAMDIR="/lib/security" \
  309. -DINSTALL_PLUGINDIR=lib/mariadb/plugin \
  310. -DINSTALL_SBINDIR=bin \
  311. -DINSTALL_SCRIPTDIR=bin \
  312. -DINSTALL_SQLBENCHDIR="" \
  313. -DINSTALL_SUPPORTFILESDIR=share/mariadb \
  314. -DINSTALL_UNIX_ADDRDIR=$(MARIADB_SOCKET) \
  315. -DMYSQL_DATADIR=/srv/mysql \
  316. -DMYSQL_UNIX_ADDR=$(MARIADB_SOCKET) \
  317. -DSKIP_TESTS=ON \
  318. -DWITH_DEBUG=OFF \
  319. -DWITH_EMBEDDED_SERVER=OFF \
  320. -DWITH_INNODB_BZIP2=OFF \
  321. -DWITH_INNODB_LZ4=OFF \
  322. -DWITH_INNODB_LZMA=ON \
  323. -DWITH_INNODB_LZO=OFF \
  324. -DWITH_INNODB_SNAPPY=OFF \
  325. -DWITH_JEMALLOC=OFF \
  326. -DWITH_LIBARCHIVE=OFF \
  327. -DWITH_LIBWRAP=OFF \
  328. -DWITH_MARIABACKUP=ON \
  329. -DWITH_NUMA=OFF \
  330. -DWITH_PCRE=system \
  331. -DWITH_SAFEMALLOC=OFF \
  332. -DWITH_SSL=system \
  333. -DWITH_SYSTEMD=no \
  334. -DWITH_VALGRIND=OFF \
  335. -DWITH_ZLIB=system
  336. # Help MariaDB find the correct libiconv.
  337. # nls.mk sets it up so that with CONFIG_BUILD_NLS libiconv-full would be used,
  338. # otherwise libiconv-stub (independent of the selected libc). MariaDB needs a
  339. # leg up to find/pick the right lib.
  340. CMAKE_OPTIONS += \
  341. -DICONV_INCLUDE_DIR=$(ICONV_PREFIX)/include \
  342. -DICONV_LIBRARIES=$(ICONV_PREFIX)/lib/libiconv.$(if $(CONFIG_BUILD_NLS),so,a)
  343. CMAKE_OPTIONS += \
  344. $(foreach p,$(MARIADB_SERVER_PLUGINS),-D$(plugin-$(p))=$(if $(CONFIG_PACKAGE_$(PKG_NAME)-server-plugin-$(subst _,-,$(p))),DYNAMIC,NO))
  345. # Disable some client library plugins
  346. CMAKE_OPTIONS += \
  347. -DCLIENT_PLUGIN_AUTH_GSSAPI_CLIENT=OFF \
  348. -DCLIENT_PLUGIN_REMOTE_IO=OFF
  349. # Set CMAKE_FIND_ROOT_PATH_MODE_INCLUDE and CMAKE_FIND_ROOT_PATH_MODE_LIBRARY
  350. # to BOTH as otherwise the host build will not find some required dependencies
  351. # installed on the host machine, like ncurses.
  352. #
  353. # Add "$(STAGING_DIR_HOSTPKG)/lib" to the RPATH of the host helpers,
  354. # otherwise they might not find the location of a library at run time.
  355. CMAKE_HOST_OPTIONS += \
  356. -DCMAKE_BUILD_WITH_INSTALL_RPATH=TRUE \
  357. -DCMAKE_FIND_ROOT_PATH_MODE_INCLUDE=BOTH \
  358. -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY=BOTH \
  359. -DCMAKE_INSTALL_RPATH="$(STAGING_DIR_HOSTPKG)/lib" \
  360. -DCMAKE_SKIP_RPATH=FALSE \
  361. -DWITHOUT_SERVER=OFF
  362. # Some helpers must be compiled for host in order to crosscompile MariaDB for
  363. # the target. They are then included by import_executables.cmake which is
  364. # generated during the build of the host helpers. It is not necessary to build
  365. # the whole host package, only the "import_executables" target.
  366. # -DIMPORT_EXECUTABLES=$(HOST_BUILD_DIR)/import_executables.cmake
  367. # must then be passed to cmake during target build.
  368. # See also https://mariadb.com/kb/en/mariadb/cross-compiling-mariadb/
  369. CMAKE_OPTIONS += -DIMPORT_EXECUTABLES=$(STAGING_DIR_HOSTPKG)/share/mariadb/import_executables.cmake
  370. # Disable some engines/plugins here as well - decreases the number of cmake checks.
  371. define Host/Prepare
  372. $(call Host/Prepare/Default)
  373. $(foreach e,$(MARIADB_DISABLE_ENGINES),$(call Package/mariadb/disable/engine,$(HOST_BUILD_DIR),$(e));)
  374. $(foreach p,$(MARIADB_DISABLE_PLUGINS),$(call Package/mariadb/disable/plugin,$(HOST_BUILD_DIR),$(p));)
  375. endef
  376. define Host/Compile
  377. $(call Host/Compile/Default,import_executables)
  378. endef
  379. define Host/Install
  380. $(SED) 's|$(HOST_BUILD_DIR)|$(STAGING_DIR_HOSTPKG)/share/mariadb|' $(HOST_BUILD_DIR)/import_executables.cmake
  381. $(INSTALL_DIR) $(1)/share/mariadb/{dbug,extra,scripts,sql}
  382. $(INSTALL_BIN) $(HOST_BUILD_DIR)/dbug/factorial $(1)/share/mariadb/dbug
  383. $(INSTALL_BIN) $(HOST_BUILD_DIR)/extra/comp_err $(1)/share/mariadb/extra
  384. $(INSTALL_BIN) $(HOST_BUILD_DIR)/scripts/comp_sql $(1)/share/mariadb/scripts
  385. $(INSTALL_BIN) $(HOST_BUILD_DIR)/sql/{gen_lex_hash,gen_lex_token} $(1)/share/mariadb/sql
  386. $(INSTALL_DATA) $(HOST_BUILD_DIR)/import_executables.cmake $(1)/share/mariadb
  387. endef
  388. # LIBICONV_PLUG is used in GNU's libiconv for redefinition of exports [e.g.
  389. # from libiconv_open() to iconv_open()]. But in OpenWrt this variable is not set
  390. # when building libiconv-full. So when MariaDB sets LIBICONV_PLUG it expects
  391. # iconv_open() to be available for example, which is not the case - only
  392. # libiconv_open() is. To address this prevent the variable from being set.
  393. # libiconv-stub does not use this variable, so there is no harm in always doing
  394. # this.
  395. define Build/Prepare
  396. $(call Build/Prepare/Default)
  397. $(SED) '/ADD_DEFINITIONS(-DLIBICONV_PLUG)/d' $(PKG_BUILD_DIR)/libmariadb/libmariadb/CMakeLists.txt
  398. $(foreach e,$(MARIADB_DISABLE_ENGINES),$(call Package/mariadb/disable/engine,$(PKG_BUILD_DIR),$(e));)
  399. $(foreach p,$(MARIADB_DISABLE_PLUGINS),$(call Package/mariadb/disable/plugin,$(PKG_BUILD_DIR),$(p));)
  400. endef
  401. define Package/mariadb-client/install
  402. $(INSTALL_DIR) $(1)/usr/bin
  403. $(foreach b,$(MARIADB_CLIENT),$(call Package/mariadb/install/bin,$(1),$(b));)
  404. # Install convenience links for mysqlcheck multi-call binary
  405. cd $(1)/usr/bin; $(LN) mysqlcheck mysqlanalyze
  406. cd $(1)/usr/bin; $(LN) mysqlcheck mysqlrepair
  407. cd $(1)/usr/bin; $(LN) mysqlcheck mysqloptimize
  408. endef
  409. define Package/mariadb-client-base/install
  410. $(INSTALL_DIR) $(1)$(CONF_DIR)/conf.d
  411. $(INSTALL_DATA) conf/50-mysql-clients.cnf $(1)$(CONF_DIR)/conf.d
  412. endef
  413. define Package/mariadb-client-extra/install
  414. $(INSTALL_DIR) $(1)/usr/bin
  415. $(foreach b,$(MARIADB_CLIENT_EXTRA),$(call Package/mariadb/install/bin,$(1),$(b));)
  416. endef
  417. define Package/mariadb-server/install
  418. $(INSTALL_DIR) $(1)/usr/bin
  419. $(foreach b,$(MARIADB_SERVER),$(call Package/mariadb/install/bin,$(1),$(b));)
  420. endef
  421. define Package/mariadb-server-base/install
  422. $(INSTALL_DIR) $(1)$(CONF_DIR)/conf.d
  423. $(INSTALL_DIR) $(1)$(SHARE_DIR)/charsets
  424. $(INSTALL_DIR) $(1)$(SHARE_DIR)/english
  425. $(INSTALL_DIR) $(1)/etc/config
  426. $(INSTALL_DIR) $(1)/etc/init.d
  427. $(INSTALL_BIN) files/mysqld.init $(1)/etc/init.d/mysqld
  428. $(SED) '/^[a-z]/s/^/#/' $(PKG_INSTALL_DIR)$(SHARE_DIR)/wsrep.cnf
  429. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/wsrep.cnf $(1)$(CONF_DIR)/conf.d/60-galera.cnf
  430. $(INSTALL_DATA) conf/50-server.cnf $(1)$(CONF_DIR)/conf.d
  431. $(INSTALL_CONF) files/mysqld.config $(1)/etc/config/mysqld
  432. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/charsets/* $(1)$(SHARE_DIR)/charsets
  433. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/english/errmsg.sys $(1)$(SHARE_DIR)/english
  434. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/fill_help_tables.sql $(1)$(SHARE_DIR)
  435. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/maria_add_gis_sp_bootstrap.sql $(1)$(SHARE_DIR)
  436. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_performance_tables.sql $(1)$(SHARE_DIR)
  437. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_system_tables.sql $(1)$(SHARE_DIR)
  438. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_system_tables_data.sql $(1)$(SHARE_DIR)
  439. $(INSTALL_DATA) $(PKG_INSTALL_DIR)$(SHARE_DIR)/mysql_test_db.sql $(1)$(SHARE_DIR)
  440. endef
  441. define Package/mariadb-server-extra/install
  442. $(INSTALL_DIR) $(1)/usr/bin
  443. $(INSTALL_DATA) $(PKG_INSTALL_DIR)/usr/bin/wsrep_sst_common $(1)/usr/bin
  444. $(SED) 's,/bin/bash,/bin/sh,g' $(PKG_INSTALL_DIR)/usr/bin/wsrep_sst_*
  445. $(foreach b,$(MARIADB_SERVER_EXTRA),$(call Package/mariadb/install/bin,$(1),$(b));)
  446. cd $(1)/usr/bin; $(LN) mariabackup mariadb-backup
  447. endef
  448. define BuildPlugin
  449. define Package/mariadb-server-plugin-$(subst _,-,$(1))
  450. $(call Package/mariadb/Default)
  451. TITLE:=mariadb-server plugin
  452. DEPENDS:=mariadb-server $(patsubst +%,+PACKAGE_mariadb-server-plugin-$(subst _,-,$(1)):%,$(2))
  453. ifeq ($(1),auth_pam)
  454. # Directory "auth_pam_tool_dir" is installed with mode 0750 and is only
  455. # accessible by root and the group mariadb. This way mariadb can access
  456. # the SUID binary "auth_pam_tool" contained within while others cannot.
  457. FILE_MODES:=/usr/lib/mariadb/plugin/auth_pam_tool_dir:root:mariadb:0750
  458. endif
  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) $$(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. $(eval $(call HostBuild))
  490. $(eval $(call BuildPackage,mariadb-client))
  491. $(eval $(call BuildPackage,mariadb-client-base))
  492. $(eval $(call BuildPackage,mariadb-client-extra))
  493. $(eval $(call BuildPackage,mariadb-server))
  494. $(eval $(call BuildPackage,mariadb-server-base))
  495. $(eval $(call BuildPackage,mariadb-server-extra))
  496. $(eval $(call BuildPlugin,auth_ed25519,))
  497. $(eval $(call BuildPlugin,auth_gssapi,+krb5-libs))
  498. $(eval $(call BuildPlugin,auth_pam,+libpam))
  499. $(eval $(call BuildPlugin,auth_pam_v1,+libpam))
  500. $(eval $(call BuildPlugin,disks,))
  501. $(eval $(call BuildPlugin,feedback,))
  502. $(eval $(call BuildPlugin,file_key_management,))
  503. $(eval $(call BuildPlugin,ha_archive,))
  504. $(eval $(call BuildPlugin,ha_blackhole,))
  505. $(eval $(call BuildPlugin,ha_connect,+libxml2))
  506. $(eval $(call BuildPlugin,ha_federated,))
  507. $(eval $(call BuildPlugin,ha_federatedx,))
  508. $(eval $(call BuildPlugin,ha_sphinx,))
  509. $(eval $(call BuildPlugin,ha_spider,))
  510. $(eval $(call BuildPlugin,handlersocket,))
  511. $(eval $(call BuildPlugin,locales,))
  512. $(eval $(call BuildPlugin,metadata_lock_info,))
  513. $(eval $(call BuildPlugin,query_cache_info,))
  514. $(eval $(call BuildPlugin,query_response_time,))
  515. $(eval $(call BuildPlugin,server_audit,))
  516. $(eval $(call BuildPlugin,simple_password_check,))
  517. $(eval $(call BuildPlugin,sql_errlog,))
  518. $(eval $(call BuildPlugin,wsrep_info,))