Bug#554780: evince: FTBFS with too old gtk-doc-tools

Loïc Minier lool at dooz.org
Thu Nov 12 10:03:38 UTC 2009


severity 554780 normal
stop

        Hi

 I'm downgrading the severity because it doesn't either affect evince in
 unstable/testing (built against the latest version of packages in
 unstable/testing) nor the one in stable.

On Fri, Nov 06, 2009, Jonas Smedegaard wrote:
> When compiling on a system with gtk-doc-tools 1.10-1 (which satisfies
> declared build-dependency) then the build fails - see attached build
> log.
> 
> Fix is simple: Tighten build-dependency to "gtk-doc-tools (>= 1.11)".
> 
> Most probably related to the following, found in NEWS file of 1.11:
> 
>  o 543855 : Fix for Bug 460753 (enable vpath build in gtkdoc-mkhtml) ...

 Hmm gtk-doc is a pain to debug; the change you mention added a grep on
 the gtkdoc-mkhtml --help output to see if it supports --path; the test
 is absolutely hideous:
-       cd $(srcdir)/html && gtkdoc-mkhtml --path="$(srcdir)" $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE) $(MKHTML_OPTIONS)
+       mkhtml_options=""; \
+       gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-path"; \
+       if test "$(?)" = "0"; then \
+         mkhtml_options=--path="$(srcdir)"; \
+       fi
+       cd $(srcdir)/html && gtkdoc-mkhtml $(mkhtml_options) $(MKHTML_OPTIONS) $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE)

 but I an not sure how it would cause this output:

> Usage: gtkdoc-mkhtml MODULE DRIVER_FILE

 NB: the missing ";" after "fi" was fixed subsequently.

 I think it would be important to identify exactly which bits of gtk-doc
 cause the output of gtkdocize to rely on new gtk-doc at build-time and
 fix that in gtk-doc upstream and in stable or some bpo baseline repo.
 I can't identify them looking merely at the source right now.

    Cheers
-- 
Loïc Minier





More information about the pkg-gnome-maintainers mailing list