The bump from libtool 2.2 to libtool 2.6 causing a name collision in graphviz regarding ltdl. Here's the bottom of the build log: Making all in gvc make[3]: Entering directory `/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/work/graphviz-2.26.3/lib/gvc' CC gvlayout.lo CC gvrender.lo CC gvdevice.lo CC gvloadimage.lo CC gvcontext.lo CC gvjobs.lo CC gvplugin.lo CC gvevent.lo CC gvconfig.lo In file included from ../../lib/common/types.h:36:0, from gvplugin.c:27: ./gvcext.h:83:22: error: conflicting types for 'lt__PROGRAM__LTX_preloaded_symbols' ../../libltdl/ltdl.h:106:36: note: previous declaration of 'lt__PROGRAM__LTX_preloaded_symbols' was here make[3]: *** [gvplugin.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/work/graphviz-2.26.3/lib/gvc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/work/graphviz-2.26.3/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/work/graphviz-2.26.3' make: *** [all] Error 2 emake failed * ERROR: media-gfx/graphviz-2.26.3-r2 failed (compile phase): * emake failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 5332: Called _eapi2_src_compile * ebuild.sh, line 665: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =media-gfx/graphviz-2.26.3-r2', * the complete build log and the output of 'emerge -pqv =media-gfx/graphviz-2.26.3-r2'. * The complete build log is located at '/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/temp/environment'. * S: '/var/tmp/portage/media-gfx/graphviz-2.26.3-r2/work/graphviz-2.26.3' >>> Failed to emerge media-gfx/graphviz-2.26.3-r2, Log file: The problem should be fixed in graphviz. I'll try to produce a patch later. Reproducible: Always
Bah! Sorry for the bug spam. Its a dup. *** This bug has been marked as a duplicate of bug 339298 ***
