libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../include -I../../include -DUNIXODBC -DHAVE_UNISTD_H -DHAVE_PWD_H -DHAVE_SYS_TYPES_H -DHAVE_LONG_LONG -DSIZEOF_LONG_INT=8 -I/usr/include -D_REENTRANT -D_THREAD_SAFE -DDEBUG=1 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-long-long -Wpointer-arith -pthread -O2 -pipe -march=native -Wall -Wdeclaration-after-statement -c tls.c -fPIC -DPIC -o .libs/tls.o tls.c: In function ‘tds_ssl_init’: tls.c:886:36: error: ‘SSL {aka struct ssl_st}’ has no member named ‘state’ ret = SSL_connect(con) != 1 || con->state != SSL_ST_OK; ^~ make[4]: *** [Makefile:556: tls.lo] Error 1 ----------------------------------------------------------------- This is an unstable amd64 chroot image (named gnome-systemd-libressl-unstable_20170208-211807) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * llvm-config --version: 3.9.1 Available Java Virtual Machines: [1] icedtea-bin-8 system-vm Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] jython2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.3.0 [icedtea-bin-8]
Created attachment 463638 [details] emerge-info.txt
Created attachment 463640 [details] config.log
Created attachment 463642 [details] dev-db:freetds-1.00.13:20170213-135537.log
Created attachment 463644 [details] emerge-history.txt
Created attachment 463646 [details] environment
Created attachment 463648 [details] etc.portage.tbz2
I'm not getting this error on my end with gcc-6.3.0.
(In reply to Peter Levine from comment #7) and LibreSSL ?
(In reply to Toralf Förster from comment #8) > (In reply to Peter Levine from comment #7) > and LibreSSL ? USE="libressl" emerge -1 =dev-libs/libressl-2.5.1:0/43::gentoo =dev-db/freetds-1.00.13::gentoo Still compiles fine with gcc-6.3.0.
(In reply to Peter Levine from comment #9) I've another image here with gcc-6.3.0 and libressl 2.5.1. where it fails with the same error : desktop-libressl-abi32+64_20170215-185650
(In reply to Toralf Förster from comment #10) > (In reply to Peter Levine from comment #9) > > I've another image here with gcc-6.3.0 and libressl 2.5.1. where it fails > with the same error : desktop-libressl-abi32+64_20170215-185650 Hmmm. Has it been successfully compiled with an active gcc-5.x compiler to make sure it's really a gcc-6.x related bug?
(In reply to Peter Levine from comment #11) it works with gcc-5, or ? (well, for being 100% completeness USE flag settings might count too) : tinderbox@mr-fox ~ $ for i in ~/run/*/var/log/emerge.log; do echo; echo $i; qlop --gauge --human --list --unlist -f $i dev-db/freetds sys-devel/gcc; done /home/tinderbox/run/13.0-abi32+64_20170216-202818/var/log/emerge.log Thu Feb 16 23:33:51 2017 >>> sys-devel/gcc-5.4.0-r3 Fri Feb 17 00:08:07 2017 <<< sys-devel/gcc-4.9.4 Sun Feb 19 11:02:16 2017 >>> dev-db/freetds-1.00.13 freetds: Sun Feb 19 10:59:49 2017: 2 minutes, 27 seconds freetds: 1 times gcc: Thu Feb 16 20:54:57 2017: 2 hours, 38 minutes, 54 seconds gcc: 1 times /home/tinderbox/run/desktop_20170218-203252/var/log/emerge.log Sat Feb 18 23:56:03 2017 >>> sys-devel/gcc-6.3.0 Sun Feb 19 00:51:20 2017 <<< sys-devel/gcc-4.9.4 gcc: Sat Feb 18 20:59:59 2017: 2 hours, 56 minutes, 4 seconds gcc: 1 times /home/tinderbox/run/desktop-libressl-abi32+64_20170215-185650/var/log/emerge.log Wed Feb 15 22:26:40 2017 >>> sys-devel/gcc-6.3.0 Wed Feb 15 23:18:49 2017 <<< sys-devel/gcc-4.9.4 gcc: Wed Feb 15 19:26:23 2017: 3 hours, 17 seconds gcc: 1 times /home/tinderbox/run/desktop-stable_20170206-184215/var/log/emerge.log Tue Feb 7 00:03:08 2017 >>> sys-devel/gcc-5.4.0-r3 Tue Feb 7 00:44:37 2017 <<< sys-devel/gcc-4.9.4 Tue Feb 14 20:42:48 2017 >>> dev-db/freetds-0.91 freetds: Tue Feb 14 20:40:52 2017: 1 minute, 56 seconds freetds: 1 times gcc: Mon Feb 6 20:58:34 2017: 3 hours, 4 minutes, 34 seconds gcc: 1 times /home/tinderbox/run/hardened_20170217-144156/var/log/emerge.log Fri Feb 17 17:53:35 2017 >>> sys-devel/gcc-5.4.0-r3 Fri Feb 17 18:34:05 2017 <<< sys-devel/gcc-4.9.4 Sat Feb 18 23:13:24 2017 >>> dev-db/freetds-1.00.13 freetds: Sat Feb 18 23:11:11 2017: 2 minutes, 13 seconds freetds: 1 times gcc: Fri Feb 17 15:09:48 2017: 2 hours, 43 minutes, 47 seconds gcc: 1 times /home/tinderbox/run/plasma-abi32+64_20170216-195507/var/log/emerge.log Thu Feb 16 23:16:52 2017 >>> sys-devel/gcc-5.4.0-r3 Fri Feb 17 00:03:21 2017 <<< sys-devel/gcc-4.9.4 Sat Feb 18 08:06:14 2017 >>> dev-db/freetds-1.00.13 freetds: Sat Feb 18 08:04:01 2017: 2 minutes, 13 seconds freetds: 1 times gcc: Thu Feb 16 20:37:03 2017: 2 hours, 39 minutes, 49 seconds gcc: 1 times /home/tinderbox/run/plasma-systemd_20170215-191016/var/log/emerge.log Wed Feb 15 22:28:13 2017 >>> sys-devel/gcc-5.4.0-r3 Wed Feb 15 23:16:51 2017 <<< sys-devel/gcc-4.9.4 Sun Feb 19 11:01:26 2017 >>> dev-db/freetds-1.00.13 freetds: Sun Feb 19 10:58:57 2017: 2 minutes, 29 seconds freetds: 1 times gcc: Wed Feb 15 19:47:06 2017: 2 hours, 41 minutes, 7 seconds gcc: 1 times
(In reply to Toralf Förster from comment #12) > (In reply to Peter Levine from comment #11) > it works with gcc-5, or ? (well, for being 100% completeness USE flag > settings might count too) : OK. I'm able to reproduce the bug with USE="-gnutls libressl". The bug depends on both USE flags. I'm able to reproduce the bug when building with gcc-5.4.0 and with gcc-6.3.0, so it doesn't seem to be gcc-6 related.
please try with =dev-db/freetds-1.00.41
