From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: moving gcc-5.2 to unstable
Date: Fri, 2 Oct 2015 10:44:11 -0400 [thread overview]
Message-ID: <560E983B.4090304@gentoo.org> (raw)
In-Reply-To: <CAJ0EP43=MuVj3g1UyKW5JhT4cgG5J45ALpQeotAsGq_ChjpqsA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/2/2015 10:27 AM, Mike Gilbert wrote:
> On Fri, Oct 2, 2015 at 4:21 AM, Ryan Hill <rhill@gentoo.org>
> wrote:
>> On Thu, 1 Oct 2015 09:49:47 -0400 Mike Frysinger
>> <vapier@gentoo.org> wrote: I think we need a news item to remind
>> people they really do have to emerge -e @world after this one or
>> they could have a bad time.
>
> I was able to get by with a targeted revdep-rebuild run.
>
> revdep-rebuild --library 'libstdc\+\+\.so\.6'
>
> The backslashes are significant since revdep-rebuild passes the
> expression to grep -E.
>
> Is there any reason to rebuild programs that do not link with the
> C++ standard library?
>
I would propose:
revdep-rebuild --library 'libstdc\+\+\.so\.6' -- --exclude sys-devel/gcc
I don't think we really need to have gcc rebuild itself for the ABI
change.
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQIcBAEBAgAGBQJWDpg6AAoJENH3ge/59KO2jqAP/2VrtExN7vWd0M2dN9te0B0H
/3tkMpxj4llQHo30oDNHISrADz/lBH1Q+c5YImQgOx+kfFMWlzqSsTS5F2KlnOHl
lpYJu3BQ24wh5R84PagHbf2FpKZm8d50pN4dH0n0fry9A/khZxnLfDjpjuTTdHLN
GWNl4HWdcMyVlFv/Hj8Yx4PVamgF7XqJsu+gD0reawNimjudgOq8q3Q4fUHhK1/0
1znKYRknA0DfSWUmyX8NTPkBaqYEBnB0aD/QZ9tcWXeR6F9+mCkmkNtCR6J3ds4B
DzXqWjGH5ZpT1DO4bsyh+X2AoLd4j5DzIJT3pNPW/PUya3O3yH2r6gJhYXxolf/s
lLJi10aYLFEwswZ4ZcjkgOQCti8Xvn6fK1/D/EC8MUmUnWYogNS2ulf2/iUlU01q
JH+MLdE76j0KGa1vJNJN8fB6z7CuoOsLY/q7FNrVR3XXsyMKPoIxmsyPFfXX+y07
SWnO3tGLfZ+q82SvnX40ynnGPdl9Sp6nu/fya7liKjmtijdWNW9ZNpfw/qLGNJyb
+CT5qnzRitfVwRr1CgY9K7ZCTCdLs8Qw4VkJHk+QNH5ggMsvA651MyCJZmUJ6lRN
1KEVAsT29U1nVo+oMQggj3VMY5Lqvk0Fe8ScF2unS4ts32/udlareWHK6o1T5PcU
/7+orcUb1IODrKlfADrc
=pkRt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-10-02 14:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 13:49 [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-10-01 14:11 ` Alexandre Rostovtsev
2015-10-01 14:24 ` Mike Frysinger
2015-10-01 15:10 ` Alexandre Rostovtsev
2015-10-01 14:34 ` Georg Rudoy
2015-10-01 20:04 ` Anthony G. Basile
2015-10-02 8:21 ` [gentoo-dev] " Ryan Hill
2015-10-02 13:56 ` Mike Frysinger
2015-10-02 14:27 ` Mike Gilbert
2015-10-02 14:44 ` Brian Evans [this message]
2015-10-03 2:13 ` [gentoo-dev] gcc-5 news item wrt C++ ABI Mike Frysinger
2015-10-03 4:53 ` [gentoo-dev] " Ryan Hill
2015-10-03 5:04 ` [gentoo-dev] " Jason Zaman
2015-10-03 8:37 ` [gentoo-dev] " Ryan Hill
2015-10-03 12:38 ` [gentoo-dev] " Ciaran McCreesh
2015-10-03 17:24 ` Mike Frysinger
2015-10-03 17:30 ` Ciaran McCreesh
2015-10-05 18:43 ` Paweł Hajdan, Jr.
2015-10-06 4:43 ` Mike Frysinger
2015-10-03 23:16 ` hasufell
2015-10-03 23:53 ` Anthony G. Basile
2015-10-04 3:58 ` [gentoo-dev] " Duncan
2015-10-20 18:17 ` [gentoo-dev] " Mike Frysinger
2015-10-06 4:49 ` Mike Frysinger
2015-10-06 5:43 ` Michał Górny
2015-10-05 18:45 ` Paweł Hajdan, Jr.
2015-10-05 19:20 ` Jason A. Donenfeld
2015-10-06 4:46 ` Mike Frysinger
2015-10-17 10:07 ` Anthony G. Basile
2015-10-22 13:57 ` Mike Frysinger
2015-12-20 21:31 ` Mike Gilbert
2015-10-29 21:18 ` [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-12-09 4:28 ` [gentoo-dev] moving gcc-5.3 " Mike Frysinger
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=560E983B.4090304@gentoo.org \
--to=grknight@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