Bug 12725

Summary: libXcomposite fails to build from git without xmlto
Product: xorg Reporter: Oswald Buddenhagen <ossi>
Component: Lib/otherAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: minor    
Priority: medium CC: esigra, jeremyhu
Version: git   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Oswald Buddenhagen 2007-10-07 04:29:49 UTC
libXcomposite finds that xmlto is missing and warns about this, but still tries to build the man page. consequently the build fails.
Comment 1 Alan Coopersmith 2007-10-07 23:32:09 UTC
If you don't have xmlto, use the tarballs which have the man pages already 
generated instead of building from git.
Comment 2 Peter Hutterer 2007-10-08 07:18:52 UTC
(In reply to comment #1)
> If you don't have xmlto, use the tarballs which have the man pages already 
> generated instead of building from git.

it'd still be a good idea to fix up the configure script to either not build the man pages if xmlto isn't installed (preferred) or just fail during configure. the current behaviour can be quite annoying. 

Comment 3 Peter Hutterer 2008-04-22 01:05:08 UTC
Simple patch, but better than the error.

diff --git a/man/Makefile.am b/man/Makefile.am
index 8ff4f37..6a6ba31 100644
--- a/man/Makefile.am
+++ b/man/Makefile.am
@@ -74,4 +74,5 @@ if HAVE_XMLTO
 else
 .xml.man:
        @echo "WARNING: configure did not find xmlto, cannot create $@ without it"
+       touch $@
 endif
Comment 4 Alan Coopersmith 2008-04-24 19:12:27 UTC
Removing from the release blocker list since this only affects builds from
git, not builds of released tarballs.
Comment 5 Jesse Adkins 2010-10-24 19:56:08 UTC
I checked and this is no longer an issue in the latest git. I assume it was fixed by 213cf861e8a29c6f991828beb6656239206c9947 using XORG_WITH_XMLTO to check for xmlto. Closing this bug.

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.