[gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

[gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

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?

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]

Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

[Mike Gilbert]

On Wed, Jul 23, 2014 at 1:48 PM, "Paweł Hajdan, Jr."
<phajdan.jr@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.

Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

[Georg Rudoy]

2014-07-29 20:28 GMT+04:00 Mike Gilbert <floppym@gentoo.org>:
> A third option that comes from the chromium-packagers ML:
>
> 3. Download and use the pre-built clang binaries from the Chromium project.

As a proxy maintainer of a package that also utilizes C++11
extensively in late releases, I'm also rather interested in having
gcc-4.8 in stable, or, otherwise, in solution #1 from the original
mail.

I remember though when I wrote in this maillist a few months ago about
having a build dep on clang I got an impression that it would be
rather inconvenient and discouraged, though feasible.

-- 
  Georg Rudoy

Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

Dnia 2014-07-23, o godz. 19:48:17
""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> napisał(a):

> 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?

For the record: https://bugs.gentoo.org/show_bug.cgi?id=516152

I think 4.8 should be our current choice for stable since 4.7 is
unsupported upstream and 4.7.4 (4.7.3 is stable now) has known unfixed
bugs.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On 7/29/14 6:49 PM, Michał Górny wrote:
> Dnia 2014-07-23, o godz. 19:48:17
> ""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> napisał(a):
> 
>> 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?
> 
> For the record: https://bugs.gentoo.org/show_bug.cgi?id=516152
> 
> I think 4.8 should be our current choice for stable since 4.7 is
> unsupported upstream and 4.7.4 (4.7.3 is stable now) has known unfixed
> bugs.

Sounds good, should we set a specific version as a stabilization target?

I'm successfully using 4.8.3 here.

Paweł



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]