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
