Bug 30826

Summary: Can't compile wine 1.3.4-git of 12th October 2010
Product: xorg Reporter: fdelente
Component: Lib/otherAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: blocker    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description fdelente 2010-10-13 03:47:49 UTC 
When trying to compile wine today, I got this error:

xvidmode.c:60: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
xvidmode.c:64: error: ‘XF86VidModeGetAllModeLines’ undeclared here (not in a function)
xvidmode.c:64: warning: type defaults to ‘int’ in declaration of ‘pXF86VidModeGetAllModeLines’
xvidmode.c:65: error: ‘XF86VidModeGetModeLine’ undeclared here (not in a function)

It seems xf86vidmodproto has changed since Xorg-server-1.8.2 and wine has not adapted. I have filed a bug on the wine bugzilla too.
Comment 1 Alan Coopersmith 2010-10-13 08:03:17 UTC 
xf86vidmodeproto is not part of the X server, it defines the protocol
between the server & clients.   Changes to it are independent of the
xorg-server version.

If you are using xf86vidmodeproto 2.3 or later, then you need to also
be using libXxf86vm 1.1.0 or later - the <X11/extensions/xf86vmode.h>
header moved between them, but the contents should be the same (and
that happened last year - this isn't new).

Even the latest git still defines those function in xf86vmode.h though:

Bool XF86VidModeGetModeLine(
    Display*                    /* dpy */,
    int                         /* screen */,
    int*                        /* dotclock */,
    XF86VidModeModeLine*        /* modeline */
);

Bool XF86VidModeGetAllModeLines(
    Display*                    /* dpy */,
    int                         /* screen */,
    int*                        /* modecount */,
    XF86VidModeModeInfo***      /* modelinesPtr */
);

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.