Bug 7161 - PolicyKit gives no error message at configure time if xmlto not installed
Summary: PolicyKit gives no error message at configure time if xmlto not installed
Status: RESOLVED INVALID
Alias: None
Product: PolicyKit
Classification: Unclassified
Component: libpolkit (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: David Zeuthen (not reading bugmail)
QA Contact: David Zeuthen (not reading bugmail)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-08 18:11 UTC by Elijah Newren
Modified: 2009-10-21 10:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Show error at configure time if xmlto not found and building docbook docs (916 bytes, patch)
2006-06-08 18:13 UTC, Elijah Newren
Details | Splinter Review

Description Elijah Newren 2006-06-08 18:11:36 UTC
If xmlto is not installed and docbook documentation is built, the following
error message occurs at build time:

no html-nochunks polkit-spec.xml
make[3]: no: Command not found
make[3]: *** [polkit-spec.html] Error 127
make[3]: Leaving directory `/floss/building/gnome/PolicyKit/doc/spec'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/floss/building/gnome/PolicyKit/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/floss/building/gnome/PolicyKit'
make: *** [all] Error 2

This is caused by XMLTO being set to 'no' by configure.  This has tripped up a
few people trying to build all of Gnome + dependencies.  I'll attach a patch in
a minute the provides an error message shown at configure time.
Comment 1 Elijah Newren 2006-06-08 18:13:17 UTC
Created attachment 5857 [details] [review]
Show error at configure time if xmlto not found and building docbook docs
Comment 2 David Zeuthen (not reading bugmail) 2009-10-21 10:28:29 UTC
This bug report is for the old version of PolicyKit. Closing as all of the code has been rewritten. Please reopen if the bug report applies to the latest version of PolicyKit. Thanks.


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.