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 459725 - "jhbuild build gtk-doc" fails on make
"jhbuild build gtk-doc" fails on make
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other All
: Normal blocker
: 1.9
Assigned To: gtk-doc maintainers
gtk-doc maintainers
: 458911 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-23 21:43 UTC by Nathan R. Yergler
Modified: 2007-09-22 19:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Transcript of the failed build process. (530.94 KB, text/plain)
2007-07-23 21:46 UTC, Nathan R. Yergler
Details

Description Nathan R. Yergler 2007-07-23 21:43:03 UTC
Please describe the problem:
When attempting to building gnome using jhbuild, it fails during the make process of gtk-doc.  In an attempt to isolate the problem I ran "jhbuild build --clean gtk-doc" and the symptoms remained with the same error message.


Steps to reproduce:
1. bootstrap jhbuild
2. run jhbuild build gtk-doc
3. there is no step 3 :)


Actual results:
The build fails.

Expected results:
The build succeeds :).

Does this happen every time?
Yes.

Other information:
Comment 1 Nathan R. Yergler 2007-07-23 21:46:17 UTC
Created attachment 92229 [details]
Transcript of the failed build process.
Comment 2 Yeti 2007-07-30 08:30:52 UTC
The transcript is quite confusing as there is no error visible.  Fortunately, I hit the same bug in a manual checkout and build.

The problem is that perl's @INC does not contain $(top_builddir), therefore the uninstalled gtkdoc-common.pl is not found.  This means that if gtk-doc is not installed at all on the machine, the build fails.  If it is installed, the system gtkdoc-common.pl is used (which makes the bug hard to hit for any gtk-doc developer) -- this is also wrong, because system gtkdoc-common.pl is not what we are trying to test.

Now someone who understands perl should figure out how to fix the search path without using a different gtk-doc.make for testing than for production -- which would sort of spoil the testing.

More remarks:

1. I don't think 2>&1 is appropriate in the command that executes gtkdoc-scangobj.  I want to *see* the errors if any occur, not a mysterious failure like this.

2. I also get failures due to missing tester-overrides.txt.  They should be created empty if not found, but it seems not early enough as I get

make[3]: *** No rule to make target `tester-overrides.txt', needed by `tmpl-build.stamp'.  Stop.
Comment 3 Yeti 2007-07-30 08:43:51 UTC
(In reply to comment #2)
> 1. I don't think 2>&1 is appropriate in the command that executes
> gtkdoc-scangobj.  I want to *see* the errors if any occur, not a mysterious
> failure like this.

If $(FOO_OPTIONS) was passed as the last thing on foo's command line in gtk-doc.make, tee could be used., i.e.

SCANGOBJ_OPTIONS = 2>&1 | tee gtkdoc-scangobj.log 

instead of

SCANGOBJ_OPTIONS = >gtkdoc-scangobj.log 2>&1

Or the tests could be run only on `make check'.
Comment 4 Stefan Sauer (gstreamer, gtkdoc dev) 2007-08-02 11:10:12 UTC
2007-08-02  Stefan Kost  <ensonic@users.sf.net>

	* tests/bugs/docs/Makefile.am:
	* tests/gobject/docs/Makefile.am:
	* tests/gtk-doc.make:
	  Use PERL5LIB envvar to use uninstalled gtkdoc-common.pl for tests.
	  Use tee to both show and redirect logs.
	  Build test-docs in check-local instead of all-local.
	  Fixes #459725.
Comment 5 Frederic Peters 2007-08-02 11:12:54 UTC
*** Bug 458911 has been marked as a duplicate of this bug. ***