Bug 6707

Summary:	problem when configuring modular Xorg on mingw
Product:	xorg	Reporter:	jason morris <jason.morris>
Component:	Build/Modular	Assignee:	Colin Harrison <colin.harrison>
Status:	RESOLVED INVALID	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	high	CC:	jon.turney
Version:	git
Hardware:	x86 (IA32)
OS:	Windows (All)
Whiteboard:
i915 platform:		i915 features:

Description jason morris 2006-04-23 20:43:56 UTC

I am running mingw on a WinXP pro platform with gcc version 3.4.5. I'm
configuring the modular Xorg package using the /util/modular/build.sh script
from CVS and when the auto-config tools check for fd_set.fds_bits it comes up
with the error "Could not determine how to access the fds_bits or equivalent
structure in fd_set on your platform." I don't know if this is a bug in Xorg or
mingw. Any help is appreciated.

Comment 1 Matthieu Herrb 2006-04-23 20:53:48 UTC

*** Bug 6708 has been marked as a duplicate of this bug. ***

Comment 2 Erik Andren 2006-04-23 21:17:58 UTC

*** Bug 6709 has been marked as a duplicate of this bug. ***

Comment 3 Erik Andren 2006-04-23 21:31:28 UTC

*** Bug 6710 has been marked as a duplicate of this bug. ***

Comment 4 jason morris 2006-04-23 22:25:23 UTC

*** Bug 6711 has been marked as a duplicate of this bug. ***

Comment 5 Daniel Stone 2007-02-27 01:31:44 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 6 Colin Harrison 2009-10-01 09:13:57 UTC

I build using MinGW on Linux for Windows by cross-compilation. This is a complex process that follow the guidelines in the X.Org documentation.

I have not tried building on Windows using MinGW/MSYS, so can't help on this query.

Comment 7 Jon Turney 2009-10-07 04:37:06 UTC

For building the XWin DDX, the only tested ways are either cross-compiling to mingw on linux, or building natively on cygwin. Anything else is untested.

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.