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 788710 - FTBFS with gtk-doc-tools 1.26
FTBFS with gtk-doc-tools 1.26
Status: RESOLVED FIXED
Product: libgoffice
Classification: Other
Component: General
0.10.x
Other Linux
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2017-10-09 12:29 UTC by Dmitry Smirnov
Modified: 2017-10-30 13:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch (887 bytes, patch)
2017-10-11 06:12 UTC, Jean Bréfort 		committed Details | Review

Description Dmitry Smirnov 2017-10-09 12:29:37 UTC 
On Debian "testing" libgoffice 0.10.35 FTBFS as follows:

    gtkdoc-scangobj: error: unrecognized arguments: --nogtkinit

After removing "--nogtkinit" from "docs/reference/Makefile.am" it FTBFS with different error:

~~~~
cd html && gtkdoc-mkhtml $mkhtml_options --path="/mnt/tmpssd/src/goffice/goffice-0.10.35/docs/reference" goffice-0.10 ../goffice-docs.xml
../xml/goffice.xml:64: parser error : error parsing attribute name
#include <goffice/goffice.h>
                 ^
../xml/goffice.xml:64: parser error : attributes construct error
#include <goffice/goffice.h>
                 ^
../xml/goffice.xml:64: parser error : Couldn't find end of Start Tag goffice line 64
#include <goffice/goffice.h>
                 ^
../goffice-docs.xml:12: element include: XInclude error : could not load ../xml/goffice.xml, and no fallback was found
~~~~
Comment 1 Jean Bréfort 2017-10-11 06:12:59 UTC 
Created attachment 361301 [details] [review]
Proposed patch
Comment 2 Morten Welinder 2017-10-30 00:29:47 UTC 
Comment on attachment 361301 [details] [review]
Proposed patch

Looks good
Comment 3 Jean Bréfort 2017-10-30 09:37:26 UTC 
Review of attachment 361301 [details] [review]:

Commited right now.
Comment 4 Jean Bréfort 2017-10-30 13:47:02 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.