Bug 19999 - The configure script produces irregular output
Summary: The configure script produces irregular output
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.4 (2008.09)
Hardware: All All
: lowest trivial
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: janitor
Depends on:
Blocks:
 
Reported: 2009-02-06 15:56 UTC by Peter Dyballa
Modified: 2011-09-25 11:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Peter Dyballa 2009-02-06 15:56:00 UTC
checking if SVR4 needs to be defined... no
	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
	checking whether to build Xgl DDX... no
	checking whether to build Xegl DDX... no
	checking whether to build Xglx DDX... no
	checking whether to build Xprint DDX... no
	checking whether to build XWin DDX... no
	checking for xp_init in -lXplugin... yes

It's obviously these lines that produce the "no" at the line beginnings:

	23488		{ $as_echo "$as_me:$LINENO: result: no" >&5
	23489	$as_echo "no" >&6; }
	23490	                have_dmx=no
	23491	elif test $pkg_failed = untried; then
	23492		have_dmx=no
	23493	else
	23494		DMXMODULES_CFLAGS=$pkg_cv_DMXMODULES_CFLAGS
	23495		DMXMODULES_LIBS=$pkg_cv_DMXMODULES_LIBS
	23496	        { $as_echo "$as_me:$LINENO: result: yes" >&5
	23497	$as_echo "yes" >&6; }
	
	24783		{ $as_echo "$as_me:$LINENO: result: no" >&5
	24784	$as_echo "no" >&6; }
	24785	                have_xnest=no
	24786	elif test $pkg_failed = untried; then
	24787		have_xnest=no
	24788	else
	24789		XNESTMODULES_CFLAGS=$pkg_cv_XNESTMODULES_CFLAGS
	24790		XNESTMODULES_LIBS=$pkg_cv_XNESTMODULES_LIBS
	24791	        { $as_echo "$as_me:$LINENO: result: yes" >&5
	24792	$as_echo "yes" >&6; }

Config.log has:

	configure:23423: checking whether to build Xdmx DDX
	configure:23427: checking for DMXMODULES
	configure:23434: $PKG_CONFIG --exists --print-errors "xmuu xext x11 xrender xfixes xfont xi dmxproto xau $XDMCP_MODULES $PIXMAN"
	configure:23437: $? = 0
	configure:23450: $PKG_CONFIG --exists --print-errors "xmuu xext x11 xrender xfixes xfont xi dmxproto xau $XDMCP_MODULES $PIXMAN"
	configure:23453: $? = 0
	configure:23488: result: yes
	configure:23495: result: no
	configure:24698: checking whether to build Xvfb DDX
	configure:24700: result: no
	configure:24718: checking whether to build Xnest DDX
	configure:24722: checking for XNESTMODULES
	configure:24729: $PKG_CONFIG --exists --print-errors "xfont xext x11 xau $XDMCP_MODULES"
	configure:24732: $? = 0
	configure:24745: $PKG_CONFIG --exists --print-errors "xfont xext x11 xau $XDMCP_MODULES"
	configure:24748: $? = 0
	configure:24783: result: yes
	configure:24790: result: no
	configure:24808: checking whether to build Xorg DDX

The intersecting "checking for ..." lines are obviously these:

	23435	{ $as_echo "$as_me:$LINENO: checking for DMXMODULES" >&5
	23436	$as_echo_n "checking for DMXMODULES... " >&6; }
	
	24730	{ $as_echo "$as_me:$LINENO: checking for XNESTMODULES" >&5
	24731	$as_echo_n "checking for XNESTMODULES... " >&6; }
Comment 1 Jeremy Huddleston Sequoia 2011-09-25 11:43:33 UTC
This looks like it was fixed at some point as it doesn't reproduce for me.


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.