Bug 18641 - ./configure sends stupid no's to stdout
Summary: ./configure sends stupid no's to stdout
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.2 (2007.02)
Hardware: PowerPC Mac OS X (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-20 09:57 UTC by Peter Dyballa
Modified: 2009-01-07 11:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Peter Dyballa 2008-11-20 09:57:11 UTC
When trying to build version xorg-server 1.4.2-apple23 configure tells me:

checking whether to build Xdmx DDX... checking for DMXMODULES... yes
no
checking whether to build Xvfb DDX... no
checking whether to build Xnest DDX... checking for XNESTMODULES... yes
no
checking whether to build Xorg DDX... no

The LOG file contains:

configure:31837: checking whether to build Xdmx DDX
configure:31841: checking for DMXMODULES
configure:31848: $PKG_CONFIG --exists --print-errors "xmuu xext x11 xrender xfixes xfont xi dmxproto xau $XDMCP_MODULES $PIXMAN"
configure:31851: $? = 0
configure:31864: $PKG_CONFIG --exists --print-errors "xmuu xext x11 xrender xfixes xfont xi dmxproto xau $XDMCP_MODULES $PIXMAN"
configure:31867: $? = 0
configure:31902: result: yes
configure:31909: result: no
configure:33112: checking whether to build Xvfb DDX
configure:33114: result: no
configure:33132: checking whether to build Xnest DDX
configure:33136: checking for XNESTMODULES
configure:33143: $PKG_CONFIG --exists --print-errors "xfont xext x11 xau $XDMCP_MODULES"
configure:33146: $? = 0
configure:33159: $PKG_CONFIG --exists --print-errors "xfont xext x11 xau $XDMCP_MODULES"
configure:33162: $? = 0
configure:33197: result: yes
configure:33204: result: no
configure:33222: checking whether to build Xorg DDX


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.