From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org, toolchain@gentoo.org
Subject: Re: [gentoo-dev] gcc-6.x status inquiry
Date: Wed, 03 May 2017 20:57:57 +0200 [thread overview]
Message-ID: <2047740.KZK34xJA38@pinacolada> (raw)
In-Reply-To: <20170503164311.GA20929@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
>
> I see that gcc-6.3 doesn't have keywords, so I'm
> wondering when it will get them? Does anyone have any idea? I'm not
> talking about stable keywords, just ~. ;-)
>
Just as a datapoint, my main dev system is ~80% stable and has been updating
with gcc-6 since beginning of february; no problems. [*] [**]
Without looking at the blockers I'd be fine with ~arch gcc-6.3 asap (so we can
eventually get gcc-7 in masked).
[*] Well I had to fix a sci-* package I'm mantaining myself, but I'm likely the
only user of it, so...
[**] That include "no problems when building firefox".
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2017-05-03 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:43 [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-03 17:10 ` Hanno Böck
2017-05-03 17:58 ` [gentoo-dev] " Luca Barbato
2017-05-03 18:00 ` Ian Stakenvicius
2017-05-03 18:42 ` William Hubbs
2017-05-03 19:06 ` Ian Stakenvicius
2017-05-03 18:44 ` Erik Närström
2017-05-04 7:28 ` grozin
2017-05-04 7:48 ` Erik Närström
2017-05-03 18:57 ` Andreas K. Huettel [this message]
2017-05-03 19:25 ` [gentoo-dev] " Matthias Maier
2017-05-04 15:22 ` Thomas Deutschmann
2017-05-04 21:32 ` Getting gcc-6 keyworded (was: Re: [gentoo-dev] gcc-6.x status inquiry) Andreas K. Huettel
2017-05-04 21:33 ` Andreas K. Huettel
2017-05-04 21:20 ` [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-04 21:30 ` Matthias Maier
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=2047740.KZK34xJA38@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=toolchain@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