In my earlier thread <http://thread.gmane.org/gmane.linux.gentoo.devel/92113> I explored the possibility to stabilize gcc-4.8, and we have that going now in <https://bugs.gentoo.org/show_bug.cgi?id=516152>.
Meanwhile I just applied a small patch for chromium-38 that allows it to compile with gcc-4.7. It's in stable now. We'll really need gcc-4.8 in stable within 6-12 weeks from now. Chromium starts making heavy use of C++11 language features, see <http://chromium-cpp.appspot.com/> . I don't realistically see us being able to just patch chromium to work around that. I'd like to ask for every possible help with <https://bugs.gentoo.org/show_bug.cgi?id=461954> blockers on amd64 and x86. There are harder problems on arches like MIPS, but newer gcc is not as urgent there I think. One highlight is <https://bugs.gentoo.org/show_bug.cgi?id=513386>. It occurs only when the user has gcc-4.7 and 4.8 installed simultaneously and using 4.7 as the active compiler. It's not obvious to me whether we have to support this (while it's obviously better to support rather than not, it's webkit-gtk in a specific and rare configuration versus chromium with security updates in all configurations). There is also <https://bugs.gentoo.org/show_bug.cgi?id=500966> which may be more tricky. I could reproduce that bug. It's also about webkit-gtk. There are couple more blockers of <https://bugs.gentoo.org/show_bug.cgi?id=461954>. If you can, please take a look and help. I think several other distros are using gcc-4.8 or later now, they may have hit the same problems and either have patches or something that could also help us. There may be some upstream patches to be backported etc. Paweł
signature.asc
Description: OpenPGP digital signature
