Bug 630274 – dev-ruby/mysql2-0.4.9 : ./mysql2_ext.h:14:23: fatal error: mysql_com.h: No such file or directory

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Toralf Förster 2017-09-07 21:05:52 UTC]

In file included from statement.c:1:0:
./mysql2_ext.h:14:23: fatal error: mysql_com.h: No such file or directory
 #include <mysql_com.h>
                       ^
compilation terminated.

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-no-multilib_20170903-173722

  -------------------------------------------------------------------

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]   pypy3 (fallback)
Available Ruby profiles:
  [1]   ruby22 (with Rubygems) *
java-config:
The following VMs are available for generation-2:


emerge -qpv dev-ruby/mysql2
[ebuild  N    ] dev-ruby/mysql2-0.4.9  USE="{-test}" RUBY_TARGETS="ruby22 -ruby23 -ruby24"

[Comment 1 Toralf Förster 2017-09-07 21:05:55 UTC]

Created attachment 493122 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-09-07 21:05:58 UTC]

Created attachment 493124 [details]
dev-ruby:mysql2-0.4.9:20170907-185141.log

[Comment 3 Toralf Förster 2017-09-07 21:06:01 UTC]

Created attachment 493126 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-09-07 21:06:04 UTC]

Created attachment 493128 [details]
environment

[Comment 5 Toralf Förster 2017-09-07 21:06:08 UTC]

Created attachment 493130 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-09-07 21:06:11 UTC]

Created attachment 493132 [details]
logs.tbz2

[Comment 7 Tomáš Mózes 2018-12-23 03:59:44 UTC]

Any news please? The github issue mentions it was fixed a year ago.

[Comment 8 Hans de Graaff 2018-12-23 10:35:07 UTC]

(In reply to Tomáš Mózes from comment #7)
> Any news please? The github issue mentions it was fixed a year ago.

Those fixes are included in mysql2 0.4.10 and 0.5.2. Furthermore it looks like mariadb 10.2.9 and newer should include compatibility patches to fix the mysql_com.h issue.

Are you still seeing this issue? If so, with which versions? Does it help to use 0.4.10-r1 and 0.5.2-r1 which link against mariadb-connector-c instead?

[Comment 9 Tomáš Mózes 2018-12-23 14:06:40 UTC]

It's a blocker to mariadb 10.2 stabilization, i don't use this actually.

[Comment 10 Hans de Graaff 2018-12-23 18:12:31 UTC]

Closing this on the assumption that this has been fixed for some time.

[Comment 11 Tomáš Mózes 2018-12-24 06:42:49 UTC]

Thanks Hans, just compile tested and it works fine.

dev-ruby/mysql2-0.4.10-r1::gentoo was built with the following:
USE="mariadb -mysql -test" ABI_X86="(64)" RUBY_TARGETS="ruby23 ruby24 -ruby25"

dev-ruby/mysql2-0.5.2-r1::gentoo was built with the following:
USE="mariadb -mysql -test" ABI_X86="(64)" RUBY_TARGETS="ruby23 ruby24 -ruby25"

dev-db/mariadb-10.2.19-r1::gentoo was built with the following:
USE="backup extraengine jemalloc pam server -bindist (-client-libs) -cracklib -debug -galera -innodb-lz4 -innodb-lzo -innodb-snappy -jdbc -kerberos -latin1 -libressl -mroonga -numa -odbc -oqgraph -perl -profiling -rocksdb (-selinux) -sphinx -sst-mariabackup -sst-rsync -sst-xtrabackup -static -systemd -systemtap -tcmalloc -test -tokudb -xml -yassl" ABI_X86="(64)"
CFLAGS="-mtune=native -O2 -pipe -fno-strict-aliasing"
CXXFLAGS="-O2 -pipe -felide-constructors -fno-strict-aliasing"