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