From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: toolchain@gentoo.org
Subject: [gentoo-dev] gcc-8 will go stable soon (~in a week)
Date: Mon, 18 Feb 2019 23:27:48 +0000 [thread overview]
Message-ID: <20190218232748.70e4d8a0@sf> (raw)
Hello world!
toolchain@ plans to start stabilizing next major gcc version
(gcc-8) in about a week at:
https://bugs.gentoo.org/678254
Current target is =sys-devel/gcc-8.2.0-r6.
If you think your bug should be absolutely addressed before
that happens please add it as a blocker.
Also feel free to cc toolchain@ explicitly on tricky build failures
without clear path to resolution. We will figure something out together.
gcc-8 was very uneventful WRT known breakages so far:
https://wiki.gentoo.org/wiki/Project:Toolchain#gcc-8
(I started it late though)
gcc porting tracker still has 3 unresoved bugs:
https://bugs.gentoo.org/show_bug.cgi?id=gcc-8
- https://bugs.gentoo.org/655206: x11-drivers/xf86-video-intel-2.99.917_p20180214 doesn't build with GCC-8.1
- https://bugs.gentoo.org/659610: app-misc/screen-4.6.2 fails with gcc-8.1.0-r3
- https://bugs.gentoo.org/664296: net-p2p/retroshare-0.6.4 : /.../stl_tree.h:452:21: error: static assertion failed: comparison object must be invocable with two arguments of key type
Please give them some love :)
Thanks!
--
Sergei
reply other threads:[~2019-02-18 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190218232748.70e4d8a0@sf \
--to=slyfox@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