Is bug 604564 sufficient reason to get a newer flex stable for gcc-6? Asking because there seem to be more problems with newer flex... and I've hit them myself too in my ~arch chroot.
The current ebuilds are not suitable for stabilization. We would need at least a rev bump and cherry-pick https://github.com/westes/flex/commit/24fd0551333e7eded87b64dd36062da3df2f6380 https://bugs.gentoo.org/628744#c2 https://github.com/westes/flex/commit/24e73c4446841eda8d4ea01298e887059e8c1472 https://bugs.gentoo.org/625508#c2 Not a big deal.
sys-devel/flex-2.6.4-r1 is now in repository via https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aa6c077d00c3a21b75ae646421aefadcad527f80 This should be fine for stabilization but let's wait a few days to settle.
@ Arches, please test and mark stable: =sys-devel/flex-2.6.4-r1 TARGET KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc x86 ~ppc-aix ~amd64-fbsd ~sparc-fbsd ~x86-fbsd ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
Stable on amd64
x86 stable
ppc/ppc64 stable
hppa/sparc stable ((thanks to Rolf Eike Beer))
ia64 stable
ping
Stable on alpha.
arm stable
arm64 stable
m68k/s390/sh stable
How about some cleanup now?