Re: X.org release engineering?
On Tue, Jun 09, 2009 at 03:04:19PM +, jspran...@awlship.com wrote: > Trying to build Kdrive and I receiving the following errors: > kinput.c: In function ‘KdEnableInput’: > kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from > incompatible pointer type > kinput.c: In function ‘KdQueueEvent’: > kinput.c:1675: warning: passing argument 2 of ‘mieqEnqueue’ from incompatible > pointer type > kinput.c: In function ‘ProcessInputEvents’: > kinput.c:2182: warning: old-style function definition > kinput.c: In function ‘NewInputDeviceRequest’: > kinput.c:2318: error: too few arguments to function ‘ActivateDevice’ > kinput.c:2319: error: too few arguments to function ‘EnableDevice’ > kinput.c:2326: error: too few arguments to function ‘ActivateDevice’ > kinput.c:2327: error: too few arguments to function ‘EnableDevice’ > kinput.c: In function ‘DeleteInputDeviceRequest’: > kinput.c:2345: error: too few arguments to function ‘RemoveDevice’ > make[3]: *** [kinput.lo] Error 1 > make[2]: *** [install-recursive] Error 1 > make[1]: *** [install-recursive] Error 1 > make: *** [install-recursive] Error 1 > can anyone point me to where I need to read to find out what I'm doing wrong? Please don't hijack threads. I have patches for this in my local tree, they will be merged soon. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: buttonmapping option
Jethro Tull wrote: > > >> Date: Wed, 3 Jun 2009 13:35:52 -0700 >> From: alan.coopersm...@sun.com >> Subject: Re: buttonmapping option >> To: heavyt...@hotmail.com >> CC: xorg@lists.freedesktop.org >> >> Jethro Tull wrote: >> > i would like to find documentation detailing all about xorg.conf input >> > device options such as buttonmapping. >> > Actually I'm trying to set my mouse as left handed and since my mouse >> > has 2 extra buttons than common mice I would like to know how to set >> > everything. >> >> That documentation, where it exists, would be in the xorg.conf man page >> for general format, and the driver-specific man pages, such as evdev >> and mouse_drv, for device-specific options. >> > option ButtonMapping is described is neither the man page of xorg.conf > nor evdev ner even in mouse. > the "Driver" line is set to mouse in my xorg.conf. Sorry, I typo'ed the man page name, there's no _: % man -M /usr/X11R7/share/man mousedrv [.] Option "ButtonMapping" "N1 N2 [...]" Specifies how physical mouse buttons are mapped to logical buttons. Physical button 1 is mapped to log- ical button N1, physical button 2 to N2, and so forth. This enables the use of physical buttons that are obscured by ZAxisMapping. Default: "1 2 3 8 9 10 ...". -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Missing symbols (_xcb_lock_io, _xcb_unlock_io)
Hi Joel, I just wanted to let you know that I'm having the same problem with today's git pull. The first time I ran into this problem was with xbacklight (which I skipped over) and then the next time I ran into it was with xrandr (which I did *NOT* skip over) which has me stopped in my tracks until I can get it to compile correctly. I've tried all kinds of things with grepping for la files and deleting la files and nothing's worked. I've even re-compiled libX11 in the hopes that it might pick up on some of the attempts at grep/deleting the *la's. If anyone has any ideas, they are most welcome. Thanks everyone! Chrelad ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xvfb - how to enable extensions (doesn't seem to be working right) XFree86-VidModeExtension
Jason Galyon wrote: > Here it is being utilized for opengl rendering in which it needs to know > screen modes. Perhaps there is a better way to extract the needed > information (resolution and depth I believe is all it needs). Screen resolution & depth are part of the core X protocol & libX11 API - you don't need any extension to get them. If it needs to know more than that what do you expect Xvfb to report? Would a screen refresh rate of 0Hz make the application happy even if it is technically correct? -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Error running Make on xorg-server-1.5.3
On Wed, 2009-06-10 at 15:32 +, jspran...@awlship.com wrote: > I'm trying to build Kdrive from the xorg-server-1.5.3 sources. > Autogen seemed to run fine with the following: > ./autogen.sh --enable-kdrive --disable-dmx --disable-dbus > --prefix=/var/tmp/xorg > > But when I run make I am getting the following output. > Can anyone give me some insight to we hat I/Ive done wrong. > > > /exa -I../../.. -I/opt/gfx-test/include -I/opt/gfx-test/include/drm > -I/usr/include/X11/dri -g -O2 -MT libxephyr_hostdri_a-XF86dri.o -MD -MP -MF > .deps/libxephyr_hostdri_a-XF86dri.Tpo -c -o libxephyr_hostdri_a-XF86dri.o > `test -f 'XF86dri.c' || echo './'`XF86dri.c > XF86dri.c:399: error: conflicting types for ‘XF86DRIDestroyContext’ > /usr/include/X11/dri/xf86dri.h:98: error: previous declaration of > ‘XF86DRIDestroyContext’ was here Current versions of xf86dri.h don't have any declarations for XF86DRI* functions. You need to upgrade to xf86driproto 2.0.4. - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
RE: Xvfb - how to enable extensions (doesn't seem to be working right)XFree86-VidModeExtension
On Tue, 2009-06-09 at 08:01 -0700, McDonald, Michael-p7438c wrote: > > extension, but since > > Xvfb doesn't connect to any monitors, the VidModeExtension > > seems pretty useless. > > Not at all! The project I'm working on runs 3 Xvfb servers and 1 Xorg > server for every desktop. Having a working VidModeExtension would be > very useful. But what would it _do_ on Xvfb? There's no physical display attached, so the concept of a modeline or gamma are pretty vacuous. - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Error running Make on xorg-server-1.5.3
I'm trying to build Kdrive from the xorg-server-1.5.3 sources. Autogen seemed to run fine with the following: ./autogen.sh --enable-kdrive --disable-dmx --disable-dbus --prefix=/var/tmp/xorg But when I run make I am getting the following output. Can anyone give me some insight to we hat I/Ive done wrong. /exa -I../../.. -I/opt/gfx-test/include -I/opt/gfx-test/include/drm -I/usr/include/X11/dri -g -O2 -MT libxephyr_hostdri_a-XF86dri.o -MD -MP -MF .deps/libxephyr_hostdri_a-XF86dri.Tpo -c -o libxephyr_hostdri_a-XF86dri.o `test -f 'XF86dri.c' || echo './'`XF86dri.c XF86dri.c:399: error: conflicting types for ‘XF86DRIDestroyContext’ /usr/include/X11/dri/xf86dri.h:98: error: previous declaration of ‘XF86DRIDestroyContext’ was here XF86dri.c:421: error: conflicting types for ‘XF86DRICreateDrawable’ /usr/include/X11/dri/xf86dri.h:101: error: previous declaration of ‘XF86DRICreateDrawable’ was here XF86dri.c:455: error: conflicting types for ‘XF86DRIDestroyDrawable’ /usr/include/X11/dri/xf86dri.h:104: error: previous declaration of ‘XF86DRIDestroyDrawable’ was here make[3]: *** [libxephyr_hostdri_a-XF86dri.o] Error 1 make[3]: Leaving directory `/home/joe/Desktop/xorg-server-1.5.3/hw/kdrive/ephyr' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/joe/Desktop/xorg-server-1.5.3/hw/kdrive' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/joe/Desktop/xorg-server-1.5.3/hw' make: *** [all-recursive] Error 1 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: X.org release engineering?
jspran...@awlship.com wrote: > Trying to build Kdrive and I receiving the following errors: > kinput.c: In function ‘KdEnableInput’: > kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from > incompatible pointer type > kinput.c: In function ‘KdQueueEvent’: > kinput.c:1675: warning: passing argument 2 of ‘mieqEnqueue’ from incompatible > pointer type > kinput.c: In function ‘ProcessInputEvents’: > kinput.c:2182: warning: old-style function definition > kinput.c: In function ‘NewInputDeviceRequest’: > kinput.c:2318: error: too few arguments to function ‘ActivateDevice’ > kinput.c:2319: error: too few arguments to function ‘EnableDevice’ > kinput.c:2326: error: too few arguments to function ‘ActivateDevice’ > kinput.c:2327: error: too few arguments to function ‘EnableDevice’ > kinput.c: In function ‘DeleteInputDeviceRequest’: > kinput.c:2345: error: too few arguments to function ‘RemoveDevice’ > make[3]: *** [kinput.lo] Error 1 > make[2]: *** [install-recursive] Error 1 > make[1]: *** [install-recursive] Error 1 > make: *** [install-recursive] Error 1 > can anyone point me to where I need to read to find out what I'm doing wrong? If you really need kdrive, this needs fixing. Adding ,TRUE to args should do the job. If you don't or don't know, don't build it. It's disabled by default. Cheers, Simon ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
