make -j1 /bin/sh /var/tmp/portage/x11-libs/libxkbcommon-0.8.2/work/libxkbcommon-0.8.2/build-aux/ylwrap /var/tmp/portage/x11-libs/libxkbcommon-0.8.2/work/libxkbcommon-0.8.2/src/xkbcomp/parser.y y.tab.c src/xkbcomp/parser.c y.tab.h `echo src/xkbcomp/parser.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output src/xkbcomp/parser.output -- bison -y -d -p _xkbcommon_ /var/tmp/portage/x11-libs/libxkbcommon-0.8.2/work/libxkbcommon-0.8.2/src/xkbcomp/parser.y:219.1-11: error: POSIX Yacc does not support %destructor [-Werror=yacc] %destructor { FreeStmt((ParseCommon *) $$); } ^~~~~~~~~~~ /var/tmp/portage/x11-libs/libxkbcommon-0.8.2/work/libxkbcommon-0.8.2/src/xkbcomp/parser.y:224.1-11: error: POSIX Yacc does not support %destructor [-Werror=yacc] ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_libressl_20190127-101048 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) emerge -qpvO x11-libs/libxkbcommon [ebuild N ] x11-libs/libxkbcommon-0.8.2 USE="X -doc -static-libs -test" ABI_X86="(64) -32 (-x32)"
Created attachment 562990 [details] emerge-info.txt
Created attachment 562992 [details] emerge-history.txt
Created attachment 562994 [details] environment
Created attachment 562996 [details] etc.portage.tbz2
Created attachment 562998 [details] logs.tbz2
Created attachment 563000 [details] temp.tbz2
Created attachment 563002 [details] x11-libs:libxkbcommon-0.8.2:20190127-161829.log
Just ran into this bug. Was able to get around it by downgrading sys-devel/ bison
This should be fixed with sys-devel/bison-3.3.1, please try again with this version. Other packages have been hitting this too, e.g. bug 676524.
(In reply to Chí-Thanh Christopher Nguyễn from comment #9) > This should be fixed with sys-devel/bison-3.3.1 indeed
