From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] mariadb: needs dynamic library support
Date: Thu, 26 Jul 2018 09:37:02 -0700 [thread overview]
Message-ID: <20180726163703.7598-2-bluemrp9@gmail.com> (raw)
In-Reply-To: <20180726163703.7598-1-bluemrp9@gmail.com>
Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
---
package/mysql/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/mysql/Config.in b/package/mysql/Config.in
index 278dc73e57..abda1880f2 100644
--- a/package/mysql/Config.in
+++ b/package/mysql/Config.in
@@ -17,6 +17,7 @@ choice
config BR2_PACKAGE_MARIADB
bool "mariadb"
depends on BR2_PACKAGE_LIBAIO_ARCH_SUPPORTS
+ depends on !BR2_STATIC_LIBS #dlopen
select BR2_PACKAGE_LIBAIO
select BR2_PACKAGE_LIBXML2
select BR2_PACKAGE_NCURSES
@@ -70,6 +71,10 @@ config BR2_PACKAGE_PROVIDES_MYSQL
endif
+comment "mariadb needs a toolchain w/ dynamic library"
+ depends on BR2_PACKAGE_LIBAIO_ARCH_SUPPORTS
+ depends on BR2_STATIC_LIBS
+
comment "mysql needs a toolchain w/ C++, threads"
depends on BR2_USE_MMU
depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
--
2.18.0
next prev parent reply other threads:[~2018-07-26 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 16:37 [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Ryan Coe
2018-07-26 16:37 ` Ryan Coe [this message]
2018-07-29 13:20 ` [Buildroot] [PATCH v2 2/3] mariadb: needs dynamic library support Thomas Petazzoni
2018-08-23 20:18 ` Peter Korsgaard
2018-07-26 16:37 ` [Buildroot] [PATCH v2 3/3] mariadb: bump version to 10.2.16 Ryan Coe
2018-08-16 21:22 ` Thomas Petazzoni
2018-08-21 13:59 ` Ryan Coe
2018-08-21 15:35 ` Thomas Petazzoni
2018-07-29 13:19 ` [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Thomas Petazzoni
2018-08-23 20:15 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180726163703.7598-2-bluemrp9@gmail.com \
--to=bluemrp9@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox