On Wed, Jul 23, 2014 at 1:48 PM, "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote: > Looks like www-client/chromium is going to start using c++11 seriously > and require gcc-4.8+, see thread > <https://groups.google.com/a/chromium.org/d/msg/chromium-packagers/fvJvPG8fa7I/iWPEsUxhKikJ> > > This is in the dev channel for now, but given the 6 weeks release cycle > it'll go to stable in about 3 months, and every time it's a security update. > > I'm trying to get Gentoo prepared now, and so what are our chances to > get gcc-4.8 to stable by that time? > > Possible alternative solutions: > > 1. Depend on clang, and force the build to use it. Possible problem with > this is that since chromium uses very bleeding edge clang, this can put > some strain on our system clang just as well. > > 2. Patch chromium to make it compile with gcc-4.7. This is almost always > technically possible, but can be a maintainability burden, especially if > upstream doesn't accept some parts of the patches. Also, there are known > problem with chromium, c++11 and gcc-4.7 > (<https://groups.google.com/a/chromium.org/d/msg/chromium-dev/NrtrEnoMH6g/ERRiVAQcE18J> > , although Gentoo is not affected by this one because we have newer dbus). > > WDYT? >
A third option that comes from the chromium-packagers ML: 3. Download and use the pre-built clang binaries from the Chromium project. I know we frown upon bundled binaries. However, I think that's really more a problem if the bundled code is used at runtime; maybe it would be ok to utilize pre-built build tools? The same could be applied to the [p]nacl toolchains; if I recall correctly, we currently disable nacl due to problems creating these from source.
