From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: c++14 global USE flag
Date: Mon, 27 Apr 2015 03:21:13 +0000 (UTC) [thread overview]
Message-ID: <pan$d9003$7badbf5a$bdf0d464$9159dbcd@cox.net> (raw)
In-Reply-To: CAHcsgXTrh5C9FHmPUvoTM-m8mW8+FNTSL=6Rsatwz=8GhOkXFw@mail.gmail.com
Diego Elio Pettenò posted on Sun, 26 Apr 2015 17:41:04 +0100 as excerpted:
> On 25 April 2015 at 16:57, Duncan <1i5t5.duncan@cox.net> wrote:
>
>> Of course, one thing that could make the process faster would be if C++
>> based packages were marked some way.
>
>
> revdep-rebuild --soname 'libstdc\+\+.so.*'
>
> should do the trick. Stuff that does not link the library (statically
> linked or using libsupc++) should not really matter.
Thanks. Obvious in hindsight. =:^)
Answering my own toolchain question then, for folks using portage as
PM... [wow, portage takes /awhile/ evaluating order!]...
Looks like dev-libs/gmp could be a problem. Back in the day we didn't
have it to worry about, but coreutils uses it with USE=gmp, which I'd
guess quite a few folks would have set for multi-processing support.
But gmp appears to have a C and a C++ lib (libgmpxx.so.*), and coreutils
wasn't in the above list on its own, so it would appear to be fine even
if libgmpxx.so.* is broken, so...
But obviously worth testing before each new gcc compatibility bump gets
unmasked...
Other than gmp, it looks like the old rules still apply just fine.
Upgrade gcc, gcc-config switch to the new version, and emerge --emptytree
@world, or at least revdep-rebuild --soname 'libstdc\+\+.so.*' as Diego
points out.
And as I already said, with modern hardware that takes... a morning...
well, maybe a day if you've lots of packages installed or are on a slow
(if modern) machine, not the two days plus it used to take when that was
simply accepted as the way it was. So shouldn't be a big deal.
Other than the usual upgrade bugs, then, the problem should be pretty
well restricted to servantware which can't be rebuilt; more specifically,
to C++ using servantware that can't be rebuilt. And that has always been
a problem, which the people choosing to use it have chosen to live with,
but which shouldn't hold back the free world that has chosen not to live
in such bondage.
For these people, what? Of course they used to get along when gcc's C++
was unstable before, so I guess they still can. Does libstdc++ get
builtin as static? If so it shouldn't be an issue. If not... I guess
they can preload libstdc++ from an older gcc.
So maybe a news item explaining both the gcc upgrade procedure, and how
to preload an old libstdc++, if they need to for binary-only servantware
or whatever.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-04-28 19:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 18:12 [gentoo-dev] RFC: c++14 global USE flag Maxim Koltsov
2015-04-24 18:42 ` Ciaran McCreesh
2015-04-24 18:56 ` Ian Stakenvicius
2015-04-24 19:11 ` Maxim Koltsov
2015-04-24 19:28 ` Georg Rudoy
2015-04-25 14:09 ` Anthony G. Basile
2015-04-25 15:23 ` Peter Stuge
2015-04-25 15:57 ` [gentoo-dev] " Duncan
2015-04-26 16:41 ` Diego Elio Pettenò
2015-04-27 3:21 ` Duncan [this message]
2015-04-28 20:07 ` Anthony G. Basile
2015-04-28 21:52 ` Mike Gilbert
2015-04-29 11:27 ` Anthony G. Basile
2015-05-02 21:11 ` Maxim Koltsov
2015-05-02 21:17 ` Kent Fredric
2015-05-02 22:18 ` Georg Rudoy
2015-05-02 22:30 ` Kent Fredric
2015-05-03 10:19 ` Maxim Koltsov
2015-05-03 10:51 ` Duncan
2015-05-03 14:13 ` Georg Rudoy
2015-05-04 4:36 ` Duncan
2015-05-03 14:08 ` Georg Rudoy
2015-05-03 14:04 ` Georg Rudoy
2015-05-03 19:07 ` Kent Fredric
2015-05-04 3:29 ` Duncan
2015-04-25 15:47 ` [gentoo-dev] " 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='pan$d9003$7badbf5a$bdf0d464$9159dbcd@cox.net' \
--to=1i5t5.duncan@cox.net \
--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