From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x
Date: Wed, 23 Jul 2014 19:48:17 +0200 [thread overview]
Message-ID: <53CFF561.90508@gentoo.org> (raw)
[-- 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 --]
next reply other threads:[~2014-07-24 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 17:48 "Paweł Hajdan, Jr." [this message]
2014-07-29 16:28 ` [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x Mike Gilbert
2014-07-29 16:39 ` Georg Rudoy
2014-07-29 16:49 ` Michał Górny
2014-08-17 16:32 ` "Paweł Hajdan, Jr."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CFF561.90508@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox