Bug 28382 - distcheck fails in out-of-tree builds
Summary: distcheck fails in out-of-tree builds
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-04 03:59 UTC by Will Thompson
Modified: 2011-01-17 06:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Thompson 2010-06-04 03:59:57 UTC
telepathy-gabble % make distclean
        telepathy-gabble % mkdir build; cd build
  telepathy-gabble/build % ../configure --enable-gtk-doc
  telepathy-gabble/build % make
  telepathy-gabble/build % make distcheck

yields a shitload of errors compiling extensions/_gen/svc.c. These are all because no marshallers are generated in extensions/_gen/signals-marshal.[ch], which is because no signatures are listed in extensions/_gen/signals-marshal.list.

But I can't figure out why not: extensions/_gen/all.xml — from which signals-marshal.list is generated — is correctly generated as far as I can tell.

(I think I'm probably the only person who builds Gabble out of tree and makes releases.)
Comment 1 Will Thompson 2010-06-04 05:11:43 UTC
CCing Adam — would be nice if the buildbot checked this still worked. :)
Comment 2 Jonny Lamb 2011-01-17 06:01:16 UTC
distcheck no longer fails on out-of-tree builds here. Perhaps something changed.

I saw some errors in the build log though, like when building gabble-signals-marshal.h, mostly due to having the headers in gabble/ and referring to them in src/. Not sure how to fix this -- I did initially fix it here by using absolute paths, but then that broke distcheck. Not sure. This isn't actually a build failure, but it probably could be pretty easily.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.