In file included from /var/tmp/portage/dev-db/mysql-workbench-6.3.10/work/mysql-workbench-community-6.3.10-src/library/sql.parser/source/mysys_priv.h:17:0, from /var/tmp/portage/dev-db/mysql-workbench-6.3.10/work/mysql-workbench-community-6.3.10-src/library/sql.parser/source/charset-def.cpp:17: /var/tmp/portage/dev-db/mysql-workbench-6.3.10/work/mysql-workbench-community-6.3.10-src/library/sql.parser/source/./my_global.h:926:2: error: #error "Neither int or long is of 4 bytes width" #error "Neither int or long is of 4 bytes width" ^~~~~ In file included from /var/tmp/portage/dev-db/mysql-workbench-6.3.10/work/mysql-workbench-community-6.3.10-src/library/sql.parser/source/mysys_priv.h:17:0, ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20180121-125258 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-db/mysql-workbench [ebuild N ] dev-db/mysql-workbench-6.3.9 USE="gnome-keyring -debug -doc" PYTHON_TARGETS="python2_7"
Created attachment 516422 [details] emerge-info.txt
Created attachment 516424 [details] dev-db:mysql-workbench-6.3.10:20180124-023928.log.bz2
Created attachment 516426 [details] emerge-history.txt
Created attachment 516428 [details] environment
Created attachment 516430 [details] etc.portage.tbz2
Created attachment 516432 [details] logs.tbz2
Created attachment 516434 [details] temp.tbz2
I have the same issue. root@lynxold:/root(15)# gcc-config -l [1] x86_64-pc-linux-gnu-7.3.0 * root@lynxold:/root(19)# eselect python list Available Python interpreters, in order of preference: [1] python3.6 [2] python3.4 [3] python3.5 (fallback) [4] python2.7 (fallback) [5] pypy (fallback) root@lynxold:/root(20)# eselect ruby list Available Ruby profiles: [1] ruby22 (with Rubygems) [2] ruby23 (with Rubygems) [3] ruby24 (with Rubygems) * [4] ruby25 (with Rubygems) root@lynxold:/root(26)# java-config -L The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Are there any news?
I got the same error. Looks like mysql-workbench includes the wrong header file (or maybe mariadb installs some of its header files in the wrong place). Mariadb installs two versions of my_config.h. One in /usr/include/mysql and the other one in /usr/include/mysql/server. The latter should be used by mysql-workbench. As a workaround I modified the /usr/bin/mysql_config script and set the variable pkgincludedir='/usr/include/mysql/server'.
mysql-workbench-8.x uses mysql-connector-c++ instead of the C bindings. Please test and re-open if this is still an issue with mysql-workbench 8.x.
