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 315320 - installer failure for gtk-doc-manual-C.omf.out
installer failure for gtk-doc-manual-C.omf.out
Status: RESOLVED FIXED
Product: gnome-common
Classification: Core
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: Gnome Common Maintainer(s)
Gnome Common Maintainer(s)
Depends on: 409060
Blocks:
 
 
Reported: 2005-09-06 01:03 UTC by Thomas Fitzsimmons
Modified: 2012-08-01 21:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
fix for install target problem (853 bytes, patch)
2005-09-06 01:05 UTC, Thomas Fitzsimmons
none Details | Review
(ugly) workaround for out of tree builds (1.14 KB, patch)
2007-02-17 20:21 UTC, Loïc Minier
none Details | Review
fix for out of tree builds (proposed gnome-common patch) (858 bytes, patch)
2007-02-17 20:45 UTC, Loïc Minier
committed Details | Review

Description Thomas Fitzsimmons 2005-09-06 01:03:14 UTC
Please describe the problem:
I'm seeing this build failure:

for file in gtk-doc-manual-C.omf; do \
        /home/fitzsim/bin/install-check -m 644 $file.out
/home/fitzsim/install/share/omf/gtk-doc/$file; \
done
/usr/bin/install: cannot stat `gtk-doc-manual-C.omf.out': No such file or directory
make[3]: *** [install-data-hook-omf] Error 1
make[3]: Leaving directory `/home/fitzsim/build/gtk-doc-bld/help/manual/C'

I'll attach a patch that fixes the problem.

Steps to reproduce:
1. Attempt to build gtk-doc using JHBuild.


Actual results:
The build fails.

Expected results:
The build should succeed.


Does this happen every time?
Yes.


Other information:
Comment 1 Thomas Fitzsimmons 2005-09-06 01:05:33 UTC
Created attachment 51846 [details] [review]
fix for install target problem
Comment 2 Damon Chaplin 2005-09-06 09:22:58 UTC
It works OK here, and the omf.make file is a standard build file from scrollkeeper
that is used in lots of apps. So I'm not sure what the problem is.
Comment 3 Damon Chaplin 2006-03-25 11:41:35 UTC
I'll close this as I think it was probably an odd problem on one machine.
But reopen if you still have a problem.
Comment 4 Loïc Minier 2007-02-17 20:20:11 UTC
Hi there,

I'm reopening as I get this bug too when building with builddir != srcdir.

This is due to the fact that omffiles are assumed to be below srcdir in omf.make.

I think this is a bug in omf.make, and I don't think it can be solved elegantly in gtk-doc as omf.make hardcodes:
scrollkeeper-preinstall $(docdir)/$(docname).xml $(srcdir)/$$file $$file.out

In the case of gtk-doc, builddir/help/manual/C/gtk-doc-manual-C.omf is generated from srcdir/help/manual/C/gtk-doc-manual-C.omf.in, so specifying "omffile = gtk-doc-manual-C.omf" will not find the file below srcdir like omf.make expects.

The reason for generating gtk-doc-manual-C.omf is that it includes:
<version identifier="@VERSION@" date="2005-08-01" description="GTK-Doc Manual"/>

I'm going to attach an ugly workaround which will break if you update omf.make without applying the same changes.

Bye,
Comment 5 Loïc Minier 2007-02-17 20:21:09 UTC
Created attachment 82752 [details] [review]
(ugly) workaround for out of tree builds
Comment 6 Loïc Minier 2007-02-17 20:45:26 UTC
Created attachment 82755 [details] [review]
fix for out of tree builds (proposed gnome-common patch)
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2007-12-04 14:57:04 UTC
Shouldn't this go into gtkdoc-common?
Comment 8 Stefan Sauer (gstreamer, gtkdoc dev) 2008-09-10 12:55:45 UTC
Reassigning to gnome-common.
Comment 9 David King 2012-08-01 21:50:11 UTC
Comment on attachment 82755 [details] [review]
fix for out of tree builds (proposed gnome-common patch)

Pushed to master as commit 1b2fb3fb47405908eb53d0db46329a64a1697a59, thanks.