Updating glibc gentoo
remove fflags, fcflags, cxxflags and set something sane, like the example i posted.
that is up to discussion, gentoo wiki has page for safe cflags, most of the times i saw that cxxflags where just referenced to cflags, and never ever defined itself, although it is the same in your case. Designed by Kyle Manna © 2003; Style derived from original sub Silver theme.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.9.3/temp/environment'.As suggested I tried using --newuse and --update but that didn't help. I've tried emerging 2.20-r2 as well as 2.19-r1, but the both have the same problem.emerge sys-devel/gcc * ERROR: sys-devel/gcc-4.9.3::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.9.3::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.9.3::gentoo'`.The easiest way to achieve that is by rebooting the machine after updating the sys-libs/glibc package.Note: Should you run into compilation failures while updating, please see bug 574948.
Search for updating glibc gentoo:
CFLAGS="-O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg//var/bind" CONFIG_PROTECT_MASK="/etc//etc/env.d /etc/fonts//etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync" FFLAGS="-O2 -pipe" why do you need FFLags, FCflags??