From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: c++14 global USE flag
Date: Sat, 25 Apr 2015 15:57:40 +0000 (UTC) [thread overview]
Message-ID: <pan$81bb6$2b548430$a778e709$1423c636@cox.net> (raw)
In-Reply-To: 20150425152317.20001.qmail@stuge.se
Peter Stuge posted on Sat, 25 Apr 2015 17:23:17 +0200 as excerpted:
> Anthony G. Basile wrote:
>> The way gcc is dealing with this is that it is NOT bumping the soname
>> so we can get libraries linking aginst libstdc++.so with the wrong abi
>> and you get breakage.
> ..
>> I'm not sure how to solve this one
>
> Is there any alternative to implementing the different sonames in
> Gentoo, if upstream doesn't want to do it?
How much of the toolchain is C++? Back in the day, gcc wasn't stable for
C++, but the toolchain didn't use it, so standard procedure if you
upgraded gcc was an emerge empty-tree @world (sometimes with an emerge
empty-tree @system first).
It was a bit of a pain, but gentooers accepted it as just how it was
done, often delaying the gcc upgrade until they had time to do the full
rebuild.
And that was back when emerge empty-tree @world could typically take a
couple days. What with faster machines these days, it might take a
morning...
So I really don't see it as a big problem, unless of course critical bits
of the toolchain are C++. I guess paludis is, but that's its problem,
and presumably they have workarounds. Just upgrade gcc and do the same
empty-tree rebuild we all learned to accept as part of the program back
when it took six or eight times as long...
Of course, one thing that could make the process faster would be if C++
based packages were marked some way. Then have the PM hook that mark and
only rebuild those packages, instead of the entire tree. Tho then you
miss out on the improvements for C packages, etc, with those improvements
presumably being why you'd upgrade in the first place, so for major gcc
bumps, a full empty-tree rebuild has some merit, even if it weren't
forced for C++ compatibility.
--
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-25 15:57 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 ` Duncan [this message]
2015-04-26 16:41 ` [gentoo-dev] " Diego Elio Pettenò
2015-04-27 3:21 ` Duncan
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$81bb6$2b548430$a778e709$1423c636@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