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 605211 - Many build failures with gtk-doc 1.13
Many build failures with gtk-doc 1.13
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other Linux
: Normal trivial
: 1.14
Assigned To: gtk-doc maintainers
gtk-doc maintainers
: 604290 605113 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-12-22 10:41 UTC by Vincent Untz
Modified: 2010-01-06 20:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch that restores a compatible behavior (2.49 KB, patch)
2009-12-22 11:56 UTC, Vincent Untz
none Details | Review

Description Vincent Untz 2009-12-22 10:41:42 UTC
We've rebuilt a lot of openSUSE packages with the latest gtk-doc, and now many fail with:

-- Fixing Crossreferences
cd . && gtkdoc-fixxref --module-dir=html --html-dir=/usr/share/gtk-doc/html
Use of uninitialized value $MODULE in concatenation (.) or string at /usr/bin/gtkdoc-fixxref line 171.
Use of uninitialized value $MODULE in concatenation (.) or string at /usr/bin/gtkdoc-fixxref line 171.
Can't open -sections.txt: No such file or directory at /usr/bin/gtkdoc-fixxref line 171.

Apparently, gtkdoc-fixxref now require a --module argument to work properly, but this wasn't the case before.
Comment 1 Vincent Untz 2009-12-22 11:43:00 UTC
This was introduced with commit 850664d444e5bfd14bd64753b0bf3e16eefa7264, which is:

    fixxref: also read section file to not warn about private stuff
    
    Some private stuff is auto-linked (e.g. in the case of types).
Comment 2 Vincent Untz 2009-12-22 11:56:17 UTC
Created attachment 150226 [details] [review]
Patch that restores a compatible behavior
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2009-12-22 18:32:29 UTC
Vincent, I'll do a somewhat similar patch. But please file bugs against the modules that fail instead. Its failing for them becasue they don't run gtkdocize and ship a static version of gtkdoc.make instead.
Comment 4 Yeti 2009-12-22 18:48:36 UTC
Stefan, running gtkdocize and shiping a static gtk-doc.make are two different things.

Any *ize tool or automake or autoconf are not supposed to be run during normal builds (in fact, I'd consider packages doing so broken).  Packages run *ize in autogen or the developer does it manually with whatever version of the build tools the developers use.  The result is then shipped.

That is not to say the packages should not be encouraged to update to newer gtk-doc.make, but it is not a bug to ship static gtk-doc.make.
Comment 5 Götz Waschk 2009-12-22 19:06:41 UTC
*** Bug 605113 has been marked as a duplicate of this bug. ***
Comment 6 Stefan Sauer (gstreamer, gtkdoc dev) 2009-12-22 20:34:03 UTC
Yeti, you are right. Old tarballs should work with a new version too.

Vincent, I pushed your patch, but removed the warnings, as it is not an error. Unfortunately one will get more false positives for the broken-link warnings for old tarballs, but I guess thats okay.

commit b39bb84dfb5f16c8b2977105bd5876b7b8d58a11
Author: Vincent Untz <vuntz@gnome.org>
Date:   Tue Dec 22 12:54:31 2009 +0100

    fixxref: make it work again without --module argument, Fixes #605211
    
    This restores a compatible behavior with previous versions of gtk-doc,
    which is required by many tarballs.
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2010-01-06 20:58:22 UTC
*** Bug 604290 has been marked as a duplicate of this bug. ***