GNOME Bugzilla – Bug 509192
Install failure when configured with --enable-gtk-doc: which: no gtkdoc-rebase in (...
Last modified: 2009-03-08 09:12:46 UTC
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-gtk --disable-debug --with-openldap --enable-gtk-doc --build=i686-pc-linux-gnu ... # make install: -- Installing ./html/home.png -- Installing ./html/index.html -- Installing ./html/index.sgml -- Installing ./html/left.png -- Installing ./html/right.png -- Installing ./html/style.css -- Installing ./html/up.png -- Installing ./html/index.sgml which: no gtkdoc-rebase in (/usr/lib/distcc/bin:/usr/local/sbin:/sbin:/usr/sbin:/usr/lib/portage/bin:/usr/local/bin:/bin:/usr/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.2.2:/opt/blackdown-jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03/jre/bin) make[3]: *** [install-data-local] Error 1 make[3]: Leaving directory `/var/tmp/portage/gnome-base/gconf-2.21.1/work/GConf-2.21.1/doc/gconf' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/var/tmp/portage/gnome-base/gconf-2.21.1/work/GConf-2.21.1/doc/gconf' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-base/gconf-2.21.1/work/GConf-2.21.1/doc' make: *** [install-recursive] Error 1
This is caused by bug 508897.
Created attachment 102754 [details] [review] gtkdoc-rebase.patch Workaround patch against 2.21.1 tarball; real fix is to apply patch in bug 508897 to gtk-doc.make and rerelease.
GConf-2.22.0 has been packaged with an old version of gtk-doc. While this is no longer an issue on Gentoo where we now have gtk-doc-1.10 with gtkdoc-rebase, it might be good to make sure that the next releases do in fact include the new gtk-doc makefiles. Thanks
I'm not sure what you mean here. What's the three step way to ensure no problems? :-)
I'd say this : 1) make sure that you have the correct gtk-doc version (gtkdocize --version should say at least 1.10 to be 100% safe) 2) rerun gtkdocize to update the scripts that will be bundled in the tarball. Maybe starting with a fresh svn checkout could force everything to be updated?
Closing this. Should be ok in newer tarballs.