Created attachment 304175 [details]
emerge --info and build.log
As per the summary, if one tries to compile soprano with USE=doc set in make.conf, it fails with the following:
/bin/sh: docs/html/installdox: No such file or directory
make: *** [CMakeFiles/apidox] Error 127
make: *** [CMakeFiles/apidox.dir/all] Error 2
make: *** [all] Error 2
A workaround is to disable building of documentation. Attached is the build log and emerge --info; note that the system normally has MAKEOPTS=-j4; I have disabled this in this build to make the error message more readable.
I take it you mean 2.7.4
Weird can't reproduce.
But on the other hand i have this:
root@arcarius: ~ # equery files soprano |grep doc
root@arcarius: ~ #
So I suppose it is bogus useflag that only builds something.
Could you verify that you have doxygen on your system while trying to build?
Stuart; I get this with doxygen - 1.8.0; Is this your installed version?
Thomas; it seems you have the other flaw; the ebuild is not installing the docs when generated
Created attachment 304649 [details, diff]
ebuild patch for -2.7.4
gentoo64 dev-libs # USE=doc ebuild soprano-2.7.4.ebuild clean install
gentoo64 dev-libs # ls /mnt/gen2/TmpDir/portage/dev-libs/soprano-2.7.4/image/usr/share/
dbus-1 doc soprano
(In reply to comment #0)
> Created attachment 304175 [details]
> emerge --info and build.log
> As per the summary, if one tries to compile soprano with USE=doc set in
> make.conf, it fails with the following:
> /bin/sh: docs/html/installdox: No such file or directory
installdox is no longer generated for >=doxygen-1.8.0
*** Bug 408041 has been marked as a duplicate of this bug. ***
dev-libs/soprano-2.7.5 fails with the same issue. Any news, how to handle this?
As a workaround I removed the doc USE flag from soprano.
Upstream says this is fixed in in 2.7.6
+*soprano-2.7.6 (16 May 2012)
+ 16 May 2012; Michael Palimaka <email@example.com> +soprano-2.7.6.ebuild:
+ Version bump. Install documentation correctly, based on patch by Ian Delaney
+ <firstname.lastname@example.org>. Fixes bug #406849.