libX11 configure.ac patch
Dear all, While trying to compile libX11 for nios2, I discovered that configure accidently thinks it is an os2 system (which is not the case). The failing code is a match on target_alias for *os2*. As my target_alias is nios2_linux, this also matches. I found this on 1.3.2 but verified that the same code is still present in git head. The patch below fixes this for me, but I can imagine people prefer to strengthen the match for os2 (not sure if changing *os2* to os2* will work, can't really verify that). In case further info is needed feel free to contact me directly. I am not on the list, just someone passing by to report a problem and solution. Best regards keep up the good work! Frans Index: libX11-1.3.2/configure.ac === --- libX11-1.3.2.orig/configure.ac 2010-11-05 10:30:33.825536983 +0100 +++ libX11-1.3.2/configure.ac 2010-11-05 10:31:25.913899269 +0100 @@ -202,6 +202,7 @@ # arch specific things WCHAR32=1 case $target_alias in + nios2*) os2=false ;; *os2*) os2=true ; WCHAR32=0 ;; *) ;; esac ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: libX11 configure.ac patch
On Fri, Nov 5, 2010 at 3:35 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: Dear all, While trying to compile libX11 for nios2, I discovered that configure accidently thinks it is an os2 system (which is not the case). The failing code is a match on target_alias for *os2*. As my target_alias is nios2_linux, this also matches. I found this on 1.3.2 but verified that the same code is still present in git head. The patch below fixes this for me, but I can imagine people prefer to strengthen the match for os2 (not sure if changing *os2* to os2* will work, can't really verify that). In case further info is needed feel free to contact me directly. I am not on the list, just someone passing by to report a problem and solution. Best regards keep up the good work! Frans Index: libX11-1.3.2/configure.ac === --- libX11-1.3.2.orig/configure.ac 2010-11-05 10:30:33.825536983 +0100 +++ libX11-1.3.2/configure.ac 2010-11-05 10:31:25.913899269 +0100 @@ -202,6 +202,7 @@ # arch specific things WCHAR32=1 case $target_alias in + nios2*) os2=false ;; *os2*) os2=true ; WCHAR32=0 ;; *) ;; esac I think the reason that *os2* was used is because the test is against $target_alias, and the os2 may be buried in the middle like i386-pc-os2-emx. I see three possible solutions: 1. Change to $target_os, in which case you can just test os2*. 2. Leave it as $target_alias, but change the test to *-os2*. 3. Special case nios2* as you've done here since it will catch the cpu type at the beginning. I think 1 is the most correct since really what we're trying to do is match the OS/2 operating system. Does the following work for you? diff --git a/configure.ac b/configure.ac index 5b79b43..6ec8bda 100644 --- a/configure.ac +++ b/configure.ac @@ -246,8 +246,8 @@ dnl AC_PATH_XTRA # arch specific things WCHAR32=1 -case $target_alias in - *os2*) os2=true ; WCHAR32=0 ;; +case $target_os in + os2*) os2=true ; WCHAR32=0 ;; *) ;; esac AC_SUBST(WCHAR32) Noticing now that this should really be testing $host_alias or $host_os since that's what you're building the package for. The $target* variables are really only applicable when you're building a cross compiler or something like that. That's orthogonal, but should be fixed. -- Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
tablet cursor configuration problem
Hi, I have been struggling to fix the problem listed below. It was suggested on the #xorg irc that i post the question to this list. Any help solving this would be most welcome, cheers kie # HARDWARE LIST: # 2 x dell U2311H 23 monitors # Gigabyte Silent ATI HD5750 Graphics Card 1GB DDR5 # Wacom Graphire3 tablet CTE-430/S # # running dual screens in Xinerama mode using ATI's proprietary driver # problem: # while the mouse works fine, the tablet cursor moves from the left half of screen 0 to the right half of screen 1 # meaning I cannot visit the right half of screen 0 or the left half of screen 1 with the tablet # same as this user: http://forums.debian.net/viewtopic.php?f=6t=47855 # # I have tried the following, but it seems to make no difference. # option MMonitor off # # software versions: # running debian squeeze amd64 # Linux lime 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux #/etc/X11/xorg.conf Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 Screen amdcccle-Screen[3]-1 1920 0 Option Xinerama 1 EndSection Section ServerFlags Option Xinerama on EndSection Section InputDevice Identifier stylus Driver wacom Option Device /dev/input/wacom Option Type stylus Option ScreenNo 0 Option MMonitor on EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Monitor Identifier 0-DFP2 Option VendorName ATI Proprietary Driver # Option ModelName Generic Autodetecting Monitor Option ModelName DELL U2311H Option DPMS true Option PreferredMode 1920x1080 Option TargetRefresh 60 Option Position 0 0 Option Rotate normal Option Disable false EndSection Section Monitor Identifier 0-DFP3 Option VendorName ATI Proprietary Driver # Option ModelName Generic Autodetecting Monitor Option ModelName DELL U2311H Option DPMS true Option PreferredMode 1920x1080 Option TargetRefresh 60 Option Position 0 0 Option Rotate normal Option Disable false EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx Option Monitor-DFP3 0-DFP3 Option XAANoOffscreenPixmaps true BusID PCI:3:0:0 EndSection Section Device Identifier ATI Driver fglrx Option AddARGBGLXVisuals true Option XAANoOffscreenPixmaps true EndSection Section Device Identifier amdcccle-Device[3]-1 Driver fglrx Option Monitor-DFP2 0-DFP2 Option XAANoOffscreenPixmaps true BusID PCI:3:0:0 Screen 1 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Section Screen Identifier amdcccle-Screen[3]-1 Device amdcccle-Device[3]-1 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Section Extensions Option Composite enable EndSection ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: libX11 configure.ac patch
On Fri, Nov 5, 2010 at 6:16 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: 2010/11/5 Dan Nicholson dbn.li...@gmail.com: On Fri, Nov 5, 2010 at 3:35 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: Dear all, While trying to compile libX11 for nios2, I discovered that configure accidently thinks it is an os2 system (which is not the case). The failing code is a match on target_alias for *os2*. As my target_alias is nios2_linux, this also matches. I found this on 1.3.2 but verified that the same code is still present in git head. The patch below fixes this for me, but I can imagine people prefer to strengthen the match for os2 (not sure if changing *os2* to os2* will work, can't really verify that). In case further info is needed feel free to contact me directly. I am not on the list, just someone passing by to report a problem and solution. Best regards keep up the good work! Frans Index: libX11-1.3.2/configure.ac === --- libX11-1.3.2.orig/configure.ac 2010-11-05 10:30:33.825536983 +0100 +++ libX11-1.3.2/configure.ac 2010-11-05 10:31:25.913899269 +0100 @@ -202,6 +202,7 @@ # arch specific things WCHAR32=1 case $target_alias in + nios2*) os2=false ;; *os2*) os2=true ; WCHAR32=0 ;; *) ;; esac I think the reason that *os2* was used is because the test is against $target_alias, and the os2 may be buried in the middle like i386-pc-os2-emx. I see three possible solutions: 1. Change to $target_os, in which case you can just test os2*. 2. Leave it as $target_alias, but change the test to *-os2*. 3. Special case nios2* as you've done here since it will catch the cpu type at the beginning. I think 1 is the most correct since really what we're trying to do is match the OS/2 operating system. Does the following work for you? diff --git a/configure.ac b/configure.ac index 5b79b43..6ec8bda 100644 --- a/configure.ac +++ b/configure.ac @@ -246,8 +246,8 @@ dnl AC_PATH_XTRA # arch specific things WCHAR32=1 -case $target_alias in - *os2*) os2=true ; WCHAR32=0 ;; +case $target_os in + os2*) os2=true ; WCHAR32=0 ;; *) ;; esac AC_SUBST(WCHAR32) Thanks for your quick reply! This works for me. Actually I did expect this, as my target_os is not os2* so I should get the default case. The key question is: does this work for os2 systems (and I cannot test that) Me neither, but I think it should be safe. Clearly this is intended for OS/2 the operating system. Noticing now that this should really be testing $host_alias or $host_os since that's what you're building the package for. The $target* variables are really only applicable when you're building a cross compiler or something like that. That's orthogonal, but should be fixed. That's ok. Didn't mention this, but actually this happens when cross compiling so I should be using the target_* vars as I am cross compiling a lib for the target. (nios2 is not that fast, you do not want to compile big packages like X on it). Technically, when cross compiling --target is only needed when you are building a compiler. I.e., the system that you're targetting your code to be created for. --host defines what system you'll be running the binaries on. http://www.gnu.org/software/automake/manual/automake.html#Cross_002dCompilation Do you specify just --target when you build or also --host? -- Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: libX11 configure.ac patch
2010/11/5 Dan Nicholson dbn.li...@gmail.com: On Fri, Nov 5, 2010 at 3:35 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: Dear all, While trying to compile libX11 for nios2, I discovered that configure accidently thinks it is an os2 system (which is not the case). The failing code is a match on target_alias for *os2*. As my target_alias is nios2_linux, this also matches. I found this on 1.3.2 but verified that the same code is still present in git head. The patch below fixes this for me, but I can imagine people prefer to strengthen the match for os2 (not sure if changing *os2* to os2* will work, can't really verify that). In case further info is needed feel free to contact me directly. I am not on the list, just someone passing by to report a problem and solution. Best regards keep up the good work! Frans Index: libX11-1.3.2/configure.ac === --- libX11-1.3.2.orig/configure.ac 2010-11-05 10:30:33.825536983 +0100 +++ libX11-1.3.2/configure.ac 2010-11-05 10:31:25.913899269 +0100 @@ -202,6 +202,7 @@ # arch specific things WCHAR32=1 case $target_alias in + nios2*) os2=false ;; *os2*) os2=true ; WCHAR32=0 ;; *) ;; esac I think the reason that *os2* was used is because the test is against $target_alias, and the os2 may be buried in the middle like i386-pc-os2-emx. I see three possible solutions: 1. Change to $target_os, in which case you can just test os2*. 2. Leave it as $target_alias, but change the test to *-os2*. 3. Special case nios2* as you've done here since it will catch the cpu type at the beginning. I think 1 is the most correct since really what we're trying to do is match the OS/2 operating system. Does the following work for you? diff --git a/configure.ac b/configure.ac index 5b79b43..6ec8bda 100644 --- a/configure.ac +++ b/configure.ac @@ -246,8 +246,8 @@ dnl AC_PATH_XTRA # arch specific things WCHAR32=1 -case $target_alias in - *os2*) os2=true ; WCHAR32=0 ;; +case $target_os in + os2*) os2=true ; WCHAR32=0 ;; *) ;; esac AC_SUBST(WCHAR32) Thanks for your quick reply! This works for me. Actually I did expect this, as my target_os is not os2* so I should get the default case. The key question is: does this work for os2 systems (and I cannot test that) Noticing now that this should really be testing $host_alias or $host_os since that's what you're building the package for. The $target* variables are really only applicable when you're building a cross compiler or something like that. That's orthogonal, but should be fixed. That's ok. Didn't mention this, but actually this happens when cross compiling so I should be using the target_* vars as I am cross compiling a lib for the target. (nios2 is not that fast, you do not want to compile big packages like X on it). Best regards, Frans ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: libX11 configure.ac patch
2010/11/5 Dan Nicholson dbn.li...@gmail.com: On Fri, Nov 5, 2010 at 6:16 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: 2010/11/5 Dan Nicholson dbn.li...@gmail.com: On Fri, Nov 5, 2010 at 3:35 AM, Frans Meulenbroeks fransmeulenbro...@gmail.com wrote: Dear all, While trying to compile libX11 for nios2, I discovered that configure accidently thinks it is an os2 system (which is not the case). The failing code is a match on target_alias for *os2*. As my target_alias is nios2_linux, this also matches. I found this on 1.3.2 but verified that the same code is still present in git head. The patch below fixes this for me, but I can imagine people prefer to strengthen the match for os2 (not sure if changing *os2* to os2* will work, can't really verify that). In case further info is needed feel free to contact me directly. I am not on the list, just someone passing by to report a problem and solution. Best regards keep up the good work! Frans Index: libX11-1.3.2/configure.ac === --- libX11-1.3.2.orig/configure.ac 2010-11-05 10:30:33.825536983 +0100 +++ libX11-1.3.2/configure.ac 2010-11-05 10:31:25.913899269 +0100 @@ -202,6 +202,7 @@ # arch specific things WCHAR32=1 case $target_alias in + nios2*) os2=false ;; *os2*) os2=true ; WCHAR32=0 ;; *) ;; esac I think the reason that *os2* was used is because the test is against $target_alias, and the os2 may be buried in the middle like i386-pc-os2-emx. I see three possible solutions: 1. Change to $target_os, in which case you can just test os2*. 2. Leave it as $target_alias, but change the test to *-os2*. 3. Special case nios2* as you've done here since it will catch the cpu type at the beginning. I think 1 is the most correct since really what we're trying to do is match the OS/2 operating system. Does the following work for you? diff --git a/configure.ac b/configure.ac index 5b79b43..6ec8bda 100644 --- a/configure.ac +++ b/configure.ac @@ -246,8 +246,8 @@ dnl AC_PATH_XTRA # arch specific things WCHAR32=1 -case $target_alias in - *os2*) os2=true ; WCHAR32=0 ;; +case $target_os in + os2*) os2=true ; WCHAR32=0 ;; *) ;; esac AC_SUBST(WCHAR32) Thanks for your quick reply! This works for me. Actually I did expect this, as my target_os is not os2* so I should get the default case. The key question is: does this work for os2 systems (and I cannot test that) Me neither, but I think it should be safe. Clearly this is intended for OS/2 the operating system. Noticing now that this should really be testing $host_alias or $host_os since that's what you're building the package for. The $target* variables are really only applicable when you're building a cross compiler or something like that. That's orthogonal, but should be fixed. That's ok. Didn't mention this, but actually this happens when cross compiling so I should be using the target_* vars as I am cross compiling a lib for the target. (nios2 is not that fast, you do not want to compile big packages like X on it). Technically, when cross compiling --target is only needed when you are building a compiler. I.e., the system that you're targetting your code to be created for. --host defines what system you'll be running the binaries on. http://www.gnu.org/software/automake/manual/automake.html#Cross_002dCompilation Do you specify just --target when you build or also --host? Both: from config.status: ac_cs_config='--build=x86_64-linux' '--host=nios2-linux' '--target=nios2-linux' Frans ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: [ANNOUNCE] xproto 7.0.19
2010/11/4 Gaetan Nadon mems...@videotron.ca: On Thu, 2010-11-04 at 14:58 -0600, Matt Dew wrote: What kind of garbled text? Is it basically one long line with no formatting? Yes, here is a sample: JuliuszChroboczek j...@freedesktop.org 27 February 2001, updated 30 October 2006 Updated by Jim Gettys and Juliusz Chroboczek. DPS is now obsolete. At the time when I started this project, there was no decent rendering interface for X11 other than DPS. Since then, there has been a large amount of work on a simple and clean X server extension, Xrender, which provides the basis for just such an interface. Gotcha. I noticed that using the wrong .xsl stylesheet would do that too. (Gotta love stylesheet issues.) ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
