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.

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