Hi there,

after upgrade to Debian unstable (which works much reliably that Stretch
here :)) glib2.0 stopped building with:
and there is patch for that:

Relevant parts of build log are:
checking for gtk-doc... no
configure: WARNING:
  You will not be able to create source packages with 'make dist'
  because gtk-doc >= 1.20 is not found.
checking for gtkdoc-check... gtkdoc-check.test
checking for gtkdoc-check... /usr/bin/gtkdoc-check
checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase
checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf
checking whether to build gtk-doc documentation... no

which later leads to:
Making install in docs
make[3]: Entering directory 
Making install in reference
make[4]: Entering directory 
Making install in glib
make[5]: Entering directory 
make[6]: Entering directory 
make[6]: Nothing to be done for 'install-exec-am'.
 /home/ladis/src/ptxdist/bin/install -c -m 644 
 /home/ladis/src/ptxdist/bin/install -c -m 644 ./html/up.png
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
Traceback (most recent call last):
  File "/usr/bin/gtkdoc-rebase", line 56, in <module>
  File "/usr/share/gtk-doc/python/gtkdoc/rebase.py", line 66, in run
    dir = common.GetModuleDocDir('glib-2.0')
  File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 104, in 
    path = subprocess.check_output([config.pkg_config, '--variable=prefix', 
module_name], universal_newlines=True)
  File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['/usr/bin/pkg-config', 
'--variable=prefix', 'glib-2.0']' returned non-zero exit status 1
Makefile:1009: recipe for target 'install-data-local' failed

As you can see, glib.rule is using host's tools in /usr/bin/gtkdoc-rebase,
thus failure is distribution dependent, which should not be the case.

This is just a bug report with possibility of providing fix later...


PS. Perhaps running PTXdist in very limited chroot would catch most of
such bugs earlier :)

ptxdist mailing list

Reply via email to