Hello, with USE=doc it fails to build: DOC Building HTML warning: failed to load external entity "../xml/dbus-gconnection.xml" ../dbus-glib-docs.sgml:69: element include: XInclude error : could not load ../xml/dbus-gconnection.xml, and no fallback was found warning: failed to load external entity "../xml/dbus-gobject.xml" ../dbus-glib-docs.sgml:70: element include: XInclude error : could not load ../xml/dbus-gobject.xml, and no fallback was found warning: failed to load external entity "../xml/dbus-gmessage.xml" ../dbus-glib-docs.sgml:71: element include: XInclude error : could not load ../xml/dbus-gmessage.xml, and no fallback was found warning: failed to load external entity "../xml/dbus-gmethod.xml" ../dbus-glib-docs.sgml:72: element include: XInclude error : could not load ../xml/dbus-gmethod.xml, and no fallback was found warning: failed to load external entity "../xml/dbus-gerror.xml" ../dbus-glib-docs.sgml:73: element include: XInclude error : could not load ../xml/dbus-gerror.xml, and no fallback was found warning: failed to load external entity "../xml/dbus-gproxy.xml" ../dbus-glib-docs.sgml:74: element include: XInclude error : could not load ../xml/dbus-gproxy.xml, and no fallback was found make[3]: *** [html-build.stamp] Error 6
Created attachment 325156 [details] build.log
Created attachment 325158 [details] environment
Created attachment 325160 [details] emerge --info gtk-doc version is 1.18-r1.
x11-libs/gtk+-3.4.4 fails to build the same way: DOC Building HTML warning: failed to load external entity "../../../../examples/gdk/composited-window-example.c" warning: failed to load external entity "../xml/gdktesting.xml" ../gdk-docs.sgml:45: element include: XInclude error : could not load ../xml/gdktesting.xml, and no fallback was found make[4]: *** [html-build.stamp] Error 6 It looks like something is terribly wrong with gtk-doc-1.18-r1...
Created attachment 325318 [details] build.log for gtk+
Created attachment 325320 [details] environment for gtk+
This is caused by dev-libs/libxslt-1.1.27 update as explained at: https://bugzilla.gnome.org/show_bug.cgi?id=684731#c1 And it also shows this is caused by wrong doc files provided by affected package (it's not a general gtk-doc problem) Then, please file a separate bug report for each broken package you find. @gnome team, I think we should try to revert: http://git.gnome.org/browse/libxslt/patch/?id=e669a8c7cefec93ee1bfaf59721aadc42e226d6e Until tree (and upstream) fix this, as we also need latest libxslt stabilized due security problems (#436284)
(In reply to comment #7) > @gnome team, I think we should try to revert: > http://git.gnome.org/browse/libxslt/patch/ > ?id=e669a8c7cefec93ee1bfaf59721aadc42e226d6e > > Until tree (and upstream) fix this, as we also need latest libxslt > stabilized due security problems (#436284) IMHO the solution is to finally remove the useless doc USE flag from gtk+ and all the other packages that use gtk-doc, include pre-built documentation in the tarball, and install that documentation by default no matter what USE flag.
I agree, but I don't know what gnome2.eclass changes are needed (#262491)
(In reply to comment #7) > Then, please file a separate bug report for each broken package you find. Done as bug 436612. If it will be more of them (I hope it wouldn't), then we'll need a tracker, perhaps.
Another one: bug 436710, there are some others as well.
This turned out to be a real problem with the dbus-glib-0.100 tarball: it contained a wrong and broken dbus-glib-sections.txt file. So thanks for reporting this issue! I've informed upstream at https://bugs.freedesktop.org/show_bug.cgi?id=55830 >*dbus-glib-0.100-r1 (10 Oct 2012) > > 10 Oct 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > +dbus-glib-0.100-r1.ebuild, +files/dbus-glib-0.100-dbus-glib-sections.txt: > Fix broken API docs; prevents build failure with libxslt-1.1.27 (bug #436454, > thanks to Andrew Savchenko). Install API docs in /usr/share/gtk-doc to allow > links from other packages' documentation files, and for compatibility with > standard tools like dev-util/devhelp (bug #404965).
*** Bug 456894 has been marked as a duplicate of this bug. ***
Why is this marked fixed? I just hit it last night.
(In reply to comment #14) > Why is this marked fixed? I just hit it last night. Because it's fixed in -r1 and you emerged older one
Ah, and -r1 isn't marked stable yet, though the older one is. Gotcha.
(In reply to comment #16) > Ah, and -r1 isn't marked stable yet, though the older one is. Gotcha. Bug 456972 for getting -r2 stable
Yup. I got the email when you added the dependency for this one.
