After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 543855 - Fix for Bug 460753 (enable vpath build in gtkdoc-mkhtml) broke backwards compatibility
Fix for Bug 460753 (enable vpath build in gtkdoc-mkhtml) broke backwards comp...
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other Linux
: Normal blocker
: 1.11
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-20 13:49 UTC by Mart Raudsepp
Modified: 2008-07-21 10:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mart Raudsepp 2008-07-20 13:49:45 UTC
As per http://bugzilla.gnome.org/show_bug.cgi?id=543854 and http://bugs.gentoo.org/show_bug.cgi?id=232417 the change in gtk-doc trunk for bug 460753 breaks backwards compatibility - tarballs prepared with a gtk-doc trunk snapshot (and ultimately gtk-doc-1.11 release if this is not fixed before) will fail gtk-doc documentation rebuild on systems that have an older gtk-doc release, such as 1.10, because their gtkdoc-mkhtml does not accept the --path argument that is added to gtk-doc.make and bails out with an error
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2008-07-21 08:08:47 UTC
Could you explain what you mean with a "documentation rebuild"?

You mean the disted gtkdoc.mak is causing trouble for people that build from tarballs and having older gtk-doc? If its that then the only fix I can think of is to add a "-" infront of the invokation in the gtkdoc.mak,
Comment 2 Mart Raudsepp 2008-07-21 10:44:55 UTC
under "documentation rebuild" I mean building a project out of a tarball while passing --enable-gtk-doc to configure. Tarballs typically come with the gtk-doc's already built and --enable-gtk-doc asks for a rebuild in that case.

And yes, the disted gtkdoc.make causes trouble for systems that have gtk-doc-1.10 or older installed, because the gtkdoc-mkhtml command that is called fails on these systems, because gtkdoc-mkhtml call is made with the systems version of it, and then those don't support --path argument and bail out.

Adding a "-" in front is not a solution, because then the task that gtkdoc-mkhtml (making the HTML files presumably) is not done at all either. The solution could perhaps be to not pass a --path argument if the gtkdoc-mkhtml that will be used doesn't support that.
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2008-07-21 10:47:22 UTC
Bummer, that won't help. It needs to run still :/ I went a different way.
Please check current svn and reopen if that still fails. Was more difficult
that I thought :(


2008-07-21  Stefan Kost  <ensonic@users.sf.net>

        * gtk-doc.make:
        * gtk-doc.notmpl.make:
          Only specify options if gtkdoc-mkhtml can take them. Fixes #543855.

        * gtkdoc-mkhtml.in:
          Don't use bash specific features. Be more flexible so that we can add
          more options.