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.

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