>>> Install lib_mysqludf_sys-0.0.3 into /var/tmp/portage/dev-db/lib_mysqludf_sys-0.0.3/image/ category dev-db !!! doexe: lib_mysqludf_sys.so does not exist * ERROR: dev-db/lib_mysqludf_sys-0.0.3::gentoo failed (install phase): * doexe failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_libressl_20170902-185407 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * emerge -qpv dev-db/lib_mysqludf_sys [ebuild N ] dev-db/lib_mysqludf_sys-0.0.3
Created attachment 492812 [details] emerge-info.txt
Created attachment 492814 [details] dev-db:lib_mysqludf_sys-0.0.3:20170906-132810.log
Created attachment 492816 [details] emerge-history.txt
Created attachment 492818 [details] environment
Created attachment 492820 [details] etc.portage.tbz2
This shouldn't happen as /usr/include/mysql/my_global.h is provided by mysql ebuild, what is the status of that package on your tinderbox? Is it present? With what USE flags?
(In reply to Pacho Ramos from comment #6) mr-fox / # emerge -pvq mysql [ebuild R ] virtual/mysql-5.6-r9 USE="server%* -embedded -static" mr-fox / # ls -l /usr/include/mysql/my_global.h ls: cannot access '/usr/include/mysql/my_global.h': No such file or directory mr-fox / # ls -l /usr/include/mysql/ total 164 -rw-r--r-- 1 root root 3527 Aug 17 12:05 errmsg.h -rw-r--r-- 1 root root 1602 Aug 17 12:05 ma_list.h -rw-r--r-- 1 root root 4329 Aug 17 12:05 ma_pvio.h drwxr-xr-x 2 root root 29 Sep 3 10:10 mariadb -rw-r--r-- 1 root root 17223 Aug 17 12:05 mariadb_com.h -rw-r--r-- 1 root root 2593 Aug 17 12:05 mariadb_ctype.h -rw-r--r-- 1 root root 8199 Aug 17 12:05 mariadb_dyncol.h -rw-r--r-- 1 root root 11227 Aug 17 12:05 mariadb_stmt.h -rw-r--r-- 1 root root 1557 Sep 3 10:09 mariadb_version.h -rw-r--r-- 1 root root 4111 Aug 17 12:05 ma_tls.h drwxr-xr-x 2 root root 94 Sep 3 10:10 mysql -rw-r--r-- 1 root root 43551 Sep 3 09:46 mysqld_error.h -rw-r--r-- 1 root root 40533 Sep 3 09:44 mysql.h drwxr-xr-x 4 root root 4096 Sep 3 10:10 server mr-fox / # emerge -pvq mariadb [ebuild R ] dev-db/mariadb-10.2.8 USE="backup cracklib libressl pam perl server systemd -bindist -debug -embedded -extraengine -galera -innodb-lz4 -innodb-lzo -innodb-snappy -jdbc -jemalloc -kerberos -latin1 -mroonga -numa -odbc -oqgraph -profiling -rocksdb (-selinux) -sphinx -sst-rsync -sst-xtrabackup -static -static-libs -systemtap -tcmalloc {-test} -tokudb -xml -yassl" ABI_X86="(64) -32 (-x32)"
Then, the issue is because that header is not provided by mariadb (while it works with mysql). How can we get that header from mariadb?
Hi, just stepping around here, not a user of mysqludf, but mariadb-10.1 _does_ install that header: qfile /usr/include/mysql/my_global.h dev-db/mariadb (/usr/include/mysql/my_global.h) $ pkg-config mariadb --cflags-only-I -I/usr/include/mysql -I/usr/include/mysql/.. $ /usr/bin/mysql_config --cflags -I/usr/include/mysql -I/usr/include/mysql/.. Just a shoot in the dark: Maybe `pkg-config mysql` is used instead of `pkg-config mariadb`?
(In reply to Francesco Riosa from comment #9) > Hi, just stepping around here, not a user of mysqludf, but mariadb-10.1 > _does_ install that header: > MariaDB 10.2 moves this header to /usr/include/mysql/server/. I don't know of an easy way to detect where the header is besides hard coding it. The config programs will not refer to it. Perhaps we need to patch in this location for CFLAGS. It may cause some troubles with mysql.h existing in both mysql and mysql/server though. Some interesting results may come about.
We will need a tracker bug to handle this change in headers location as it looks to break several reverse deps (at least, a lot of dev-db/lib_mysqludf* look affected by this)
(In reply to Pacho Ramos from comment #11) yep, dev-python/mysql-python-1.2.3-r1 is affected too
(In reply to Toralf Förster from comment #12) > (In reply to Pacho Ramos from comment #11) > yep, dev-python/mysql-python-1.2.3-r1 is affected too FWIW, dev-python/mysql-python can drop the "#include <my_config.h>" as it is for ancient HAVE_OPENSSL detection which is forced on with >=dev-db/{mysql,mariadb}-5.5.0
Removed from the tree
