Created attachment 521026 [details] emerge_info attempted to install media-gfx/inkscape-0.92.2 and the build fails during link time, possibly not finding Cairo libraries? Log file is 2.5MB, I'll attach the last 100 lines. [ebuild U ] media-gfx/inkscape-0.92.2 [0.91-r3] USE="dbus jpeg nls openmp -cdr* -dia -exif* -gnome -imagemagick -inkjar -latex -lcms* -postscript -spell* -static-libs -visio -wpg" PYTHON_TARGETS="python2_7"
Created attachment 521028 [details] environment
Created attachment 521030 [details] build.log - last 100 lines
Comment on attachment 521030 [details] build.log - last 100 lines Please attach the entire build log to this bug report.
(In reply to John L. Poole from comment #0) > Log file is 2.5MB, I'll attach the last 100 lines. Compress it.
Created attachment 521076 [details] build log
What was I thinking? I guess I thought build.logs needed to be readable from the start. Thanks, it compressed very nicely and is now uploaded.
This sure looks like you haven't rebuild all libstdc++ consumers after upgrading from gcc-4.x to >=5, could that be the case? Details here: https://www.gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html In this case I think a rebuild of cairo and gtkmm:2.4 will get inkscape building, but you may have many other things which still need rebuild.
Yes, I've been upgrading my system and this was the last item on the list. I got distracted by inkscape failing to build and probably neglected to revdep-rebuild as I would do that after I succeeded in getting all updates built. Interesting, I just tried this: # revdep-rebuild -- --exclude gcc * This is the new python coded version * Please report any bugs found using it. * The original revdep-rebuild script is installed as revdep-rebuild.sh * Please file bugs at: https://bugs.gentoo.org/ * Collecting system binaries and libraries * Checking dynamic linking consistency Your system is consistent # gcc-config -l [1] x86_64-pc-linux-gnu-4.9.4 [2] x86_64-pc-linux-gnu-5.4.0 [3] x86_64-pc-linux-gnu-6.4.0 * # I'll try your suggestions. In the meantime, doesn't revdep--rebuild cover this kind of thing?
The ABI change on libstdc++ wasn't accompanied by a soname change (eg libfoo.so.1 -> libfoo.so.2) so it's not the kind of breakage that revdep-rebuild is able to detect. That is why the news item tells you to do a targetted rebuild against libstdc++.so.6 -- you have to tell revdep-rebuild "rebuild everything linking to libstdc++, whether you can detect breakage there or not"
please recheck after following the instructions in https://www.gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html
