RE: Unable to get french keyboard with XDMCP connexion on AIX
Bonjour Fréderic, L'option -ac n'a rien à voir avec le clavier, si je ne me trompe pas. Il te faut les options +kb -xkbmap fr, moi j'ai un clavier belge, alors: XWin +kb -xkbmap be -auth $HOME/.Xauthority -emulate3buttons -unixkill -nowinkill Il te faut aussi un fichier avec le dessin de ton clavier, dans /tmp, chez moi: /tmp/be.xkm Tu peux génerer ce fichier avec xkbcomp, avec les sources qui se trouvent dans /usr/X11R6/lib/X11/xkb. Courage! Gérard -Original Message- From: frederic bregier [mailto:[EMAIL PROTECTED]] Sent: vrijdag 17 mei 2002 1:00 To: [EMAIL PROTECTED] Subject: Re: Unable to get french keyboard with XDMCP connexion on AIX Hi all, I try the -ac option from Pavel with XWin. I am not able to get the french keyboard at login, but just after, the xmodmap locally runned (in the local script, not on the remote server) is perfectly running and I get the french keyboard. So it is a part of the answear (since I prefer to get all the specific configuration part on my PC, not on the many server I must access). The only point is that -ac enables anyone to get access to my X client (like xhost +). But not too bad anyway. If someone find how to finaly get the french KB at logon time, and it is perfect for me. By the way, thank you all for your helps!!! Great job! Frederic - http://www.WebMailSPro.com - VOTRE service d'email sans pub avec VOTRE nom de domaine === This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. You are explicitly requested to notify the sender of this email that the intended recipient was not reached.
double keystroke effects with XP
Hi out there, I'm using cygwin on XP. Whenever I use X11 and type at normal speed, I get about every 10th character twice. If I take care and touch only one key at a time everything works fine. Any ideas? Thank you, Ralf Gans
Re: building xwin packages
Harold Hunt [EMAIL PROTECTED] wrote: http://www.msu.edu/~huntharo/xwin/XFree86-cygwin-build.tar.bz2 (3 KiB) No... Kibibytes sounds far too stupid to actually be used! Max.
Re: building xwin packages
Next thing they'll want us to start measuring temperature in Kelvin... Cheers, Nicholas --- Max Bowsher [EMAIL PROTECTED] wrote: Harold Hunt [EMAIL PROTECTED] wrote: http://www.msu.edu/~huntharo/xwin/XFree86-cygwin-build.tar.bz2 (3 KiB) No... Kibibytes sounds far too stupid to actually be used! Max. __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
RE: building xwin packages
Need to know the XWin server size / rgs, NR -Original Message- From: Harold Hunt [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 3:19 AM To: Nicholas Wourms Cc: cygx Subject: RE: building xwin packages Nicholas, Is there anything different which must be done now to cross compile that wasn't included in your directions or has changed since you wrote them? I haven't done a cross compile in a couple of months now. I just deleted by Cygwin cross compiler off of my Linux machine, so I'd have to spend a bit of time to do a test cross compile right now. I'm a little strapped for time right now and we're going out of town for the weekend, so it'll have to wait until next month sometime. On the other hand, I do recall that if you do not pass the flags *exactly* as documented the build process will usually bomb at imake. You should be using the command like so (all on one line, but I wrapped it for readability): [harold@MyCrossHost std]$ make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux World.log 21 Good luck, Harold -Original Message- From: Nicholas Wourms [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:09 PM To: Harold L Hunt Subject: Re: building xwin packages Harold, I am quite aware of the the trias involved with building Xfree (I just went trough it a few months ago on OSX ;)). Given that, I was attempting to follow the directions on in the contributor's guide regarding building Xfree. Unfortunately matters have been complicated twofold, as I am quite dissappointed with the performance of compilation on my windows machine. Therefore I was setting up a cross-compile environment on my suse 7.3 linux box per your directions. This is where I want to ask a question: Is there anything different which must be done now to crosscompile that wasn't included in your directions or has changed since you wrote them? I will follow the steps below and see if my result is different, but for some reason when I followed your directions (before you sent this mail) in the howto and double checked my process, the make process bombs out on imake.c, complaining about a imake.c:395: parse error before `1'. From what I see crosscompiling needs different defines? I'm not sure...despite that my will is strong and my desire to recompile is kindled by the desire to help in testing kde. Cheers, Nicholas --- Harold L Hunt [EMAIL PROTECTED] wrote: Nicholas, Building the XFree86 packages for Cygwin is not for the faint of heart. It takes possibly many hours (especially for first timers) and there is a lot that can go wrong. With that in mind, I'll point you to two of the three steps for building the packages, and I'll post the packaging script tonight when I am on the machine that has it. I had posted the script before but the machine it was on is no longer accessible, so I'll have to put it somewhere else. Be aware that you can start the first two steps and by the time that I post the packaging script in about 8 hours you still won't have built XFree86... 1) Follow the instructions in the Cygwin/XFree86 Contributor's Guide for downloading the source for XFree86 and building it. You'll want to grab the `xf-4_2-branch' of the source code. I think you would do that with: cvs checkout -r xf-4_2-branch xc Notice that some of the patches to the latest Xxserv package were not applied to the xf-4_2-branch (I don't think Alan keeps an xf-4_2-branch tree around) so you'll need to grab the default branch and copy the files from xc/programs/Xserver/hw/xwin/ into your 4_2 tree. The relevant steps in the Contributor's Guide are here: http://xfree86.cygwin.com/docs/cg/prog-build-native.html 2) After building XFree86 you'll need to create the XFree86 packages, which is very difficult. I've attempted to create a Cygwin-specific version of the instructions for this at: http://xfree86.cygwin.com/docs/cg/prog-distribution.html 3) Now you need to convert the XFree86 packages into Cygwin packages. This is done with the build.sh script that Ian Burrell wrote and I modified. I'll post this later tonight, but the basic idea is that you copy the XFree86 packages into a directory with build.sh, then run the script. It takes about 5 to 10 minutes on my 1200 Athlon with a pretty quick hard drive, so I wouldn't be surprised if it took up to an hour on older hardware. You'd better be really sure that you actually want to do this before you put any time into it. There is a reason that XFree86 was not installable via Cygwin's setup.exe for almost a year after we started using the XFree86 packaging script. Good luck, Harold Nicholas Wourms [EMAIL PROTECTED] said: Harold, How do you build the packages for use with setup.exe? Do you use a script or do you do it by hand? If
RE: building xwin packages
Harold, Does it seem strange for a PIII/733 running linux to produce the following results?: # time make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux make-world.log real66m36.681s user27m51.320s sys 3m5.950s Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Here is my cross compile build log so that you can see what is supposed to happen: http://www.msu.edu/~huntharo/xwin/World-cross.log.bz2 (156 KiB) Hope that helps, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nicholas Wourms Sent: Thursday, May 16, 2002 8:09 PM To: Harold Hunt Subject: RE: building xwin packages Harold, Before you go, don't forget to post the script :). Thanks in advance and have a pleasant trip! Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Nicholas, Is there anything different which must be done now to cross compile that wasn't included in your directions or has changed since you wrote them? I haven't done a cross compile in a couple of months now. I just deleted by Cygwin cross compiler off of my Linux machine, so I'd have to spend a bit of time to do a test cross compile right now. I'm a little strapped for time right now and we're going out of town for the weekend, so it'll have to wait until next month sometime. On the other hand, I do recall that if you do not pass the flags *exactly* as documented the build process will usually bomb at imake. You should be using the command like so (all on one line, but I wrapped it for readability): [harold@MyCrossHost std]$ make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux World.log 21 Good luck, Harold -Original Message- From: Nicholas Wourms [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:09 PM To: Harold L Hunt Subject: Re: building xwin packages Harold, I am quite aware of the the trias involved with building Xfree (I just went trough it a few months ago on OSX ;)). Given that, I was attempting to follow the directions on in the contributor's guide regarding building Xfree. Unfortunately matters have been complicated twofold, as I am quite dissappointed with the performance of compilation on my windows machine. Therefore I was setting up a cross-compile environment on my suse 7.3 linux box per your directions. This is where I want to ask a question: Is there anything different which must be done now to crosscompile that wasn't included in your directions or has changed since you wrote them? I will follow the steps below and see if my result is different, but for some reason when I followed your directions (before you sent this mail) in the howto and double checked my process, the make process bombs out on imake.c, complaining about a imake.c:395: parse error before `1'. From what I see crosscompiling needs different defines? I'm not sure...despite that my will is strong and my desire to recompile is kindled by the desire to help in testing kde. Cheers, Nicholas --- Harold L Hunt [EMAIL PROTECTED] wrote: Nicholas, Building the XFree86 packages for Cygwin is not for the faint of heart. It takes possibly many hours (especially for first timers) and there is a lot that can go wrong. With that in mind, I'll point you to two of the three steps for building the packages, and I'll post the packaging script tonight when I am on the machine that has it. I had posted the script before but the machine it was on is no longer accessible, so I'll have to put it somewhere else. Be aware that you can start the first two steps and by the time that I post the packaging script in about 8 hours you still won't have built XFree86... 1) Follow the instructions in the Cygwin/XFree86 Contributor's Guide for downloading the source for XFree86 and building it. You'll want to grab the `xf-4_2-branch' of the source code. I think you would do that with: cvs checkout -r xf-4_2-branch xc Notice that some of the patches to the latest Xxserv package were not applied to the xf-4_2-branch (I don't think Alan keeps an xf-4_2-branch tree around) so you'll need to grab the default branch and copy the files from xc/programs/Xserver/hw/xwin/ into your 4_2 tree. The relevant steps in the Contributor's Guide are here: http://xfree86.cygwin.com/docs/cg/prog-build-native.html 2) After building XFree86 you'll need to create the XFree86 packages, which is
Re: KDE 2.2.2 beta1 released
On Fri, 17 May 2002 09:39:23 +0200 Ralf Habacker [EMAIL PROTECTED] wrote: Hi all, today the KDE 2.2.2 beta 1 is released. For further details see http://cygwin.kde.org/kde2.php Have fun ! Ralf Habacker I had this problem with the installer for 2.2.1 as well, but I was hoping it would be fixed in this one. During the installation of kdebase, I will get about half way through, and then get booged down in a series of error messages that read: warning: deleting d:\cygwin/opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig_serverencryptionconfig_servercertificate_blurb.png so I can make a directory there. After hitting OK, I get another one that reads: warning: moving directory /opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig_serverencryptionconfig_servercertificate_blurb.png out of the way. At least for 2.2.1, installing manually by extracting the archive on the command line works. And, sure enough, I have multiple copies of a directory with that name. Will proceed with manual installation for 2.2.2. -- ** Jonathan Fosburgh |Certified AIX Administrator Software Systems Spec. III |ICQ: 32742908 Communications and Computer Services|MSN: [EMAIL PROTECTED] UT MD Anderson Cancer Center|Jabber: [EMAIL PROTECTED] Houston, TX |Yahoo: jefosburgh **
Need to know X Win server size
Hi, Need the help regarding the X Win server size with NMAKE approach on optimization. rgs, NR DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to MASCOT SYSTEMS LTD and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] Before opening attachments, Please scan for Viruses
error downloading XFree86-base-4.2.0-1.tar.bz2
when I download the XFree86-base-4.2.0-1.tar.bz2 through the cygwin setup an error occurs (the file is only 46 bytes). The installation is not proceeding after that. Is there a soluttion?
RE: error downloading XFree86-base-4.2.0-1.tar.bz2
46 bytes sounds about right. Rob -Original Message- From: Kostas Adaos [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 11:29 PM To: [EMAIL PROTECTED] Subject: error downloading XFree86-base-4.2.0-1.tar.bz2 when I download the XFree86-base-4.2.0-1.tar.bz2 through the cygwin setup an error occurs (the file is only 46 bytes). The installation is not proceeding after that. Is there a soluttion?
RE: building xwin packages
Sorry, Just discovered that SuSE uses yacc instead of byacc, therefore it really wasn't building afterall :(. Nicholas --- Nicholas Wourms [EMAIL PROTECTED] wrote: Harold, Does it seem strange for a PIII/733 running linux to produce the following results?: # time make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux make-world.log real66m36.681s user27m51.320s sys 3m5.950s Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Here is my cross compile build log so that you can see what is supposed to happen: http://www.msu.edu/~huntharo/xwin/World-cross.log.bz2 (156 KiB) Hope that helps, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nicholas Wourms Sent: Thursday, May 16, 2002 8:09 PM To: Harold Hunt Subject: RE: building xwin packages Harold, Before you go, don't forget to post the script :). Thanks in advance and have a pleasant trip! Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Nicholas, Is there anything different which must be done now to cross compile that wasn't included in your directions or has changed since you wrote them? I haven't done a cross compile in a couple of months now. I just deleted by Cygwin cross compiler off of my Linux machine, so I'd have to spend a bit of time to do a test cross compile right now. I'm a little strapped for time right now and we're going out of town for the weekend, so it'll have to wait until next month sometime. On the other hand, I do recall that if you do not pass the flags *exactly* as documented the build process will usually bomb at imake. You should be using the command like so (all on one line, but I wrapped it for readability): [harold@MyCrossHost std]$ make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux World.log 21 Good luck, Harold -Original Message- From: Nicholas Wourms [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:09 PM To: Harold L Hunt Subject: Re: building xwin packages Harold, I am quite aware of the the trias involved with building Xfree (I just went trough it a few months ago on OSX ;)). Given that, I was attempting to follow the directions on in the contributor's guide regarding building Xfree. Unfortunately matters have been complicated twofold, as I am quite dissappointed with the performance of compilation on my windows machine. Therefore I was setting up a cross-compile environment on my suse 7.3 linux box per your directions. This is where I want to ask a question: Is there anything different which must be done now to crosscompile that wasn't included in your directions or has changed since you wrote them? I will follow the steps below and see if my result is different, but for some reason when I followed your directions (before you sent this mail) in the howto and double checked my process, the make process bombs out on imake.c, complaining about a imake.c:395: parse error before `1'. From what I see crosscompiling needs different defines? I'm not sure...despite that my will is strong and my desire to recompile is kindled by the desire to help in testing kde. Cheers, Nicholas --- Harold L Hunt [EMAIL PROTECTED] wrote: Nicholas, Building the XFree86 packages for Cygwin is not for the faint of heart. It takes possibly many hours (especially for first timers) and there is a lot that can go wrong. With that in mind, I'll point you to two of the three steps for building the packages, and I'll post the packaging script tonight when I am on the machine that has it. I had posted the script before but the machine it was on is no longer accessible, so I'll have to put it somewhere else. Be aware that you can start the first two steps and by the time that I post the packaging script in about 8 hours you still won't have built XFree86... 1) Follow the instructions in the Cygwin/XFree86 Contributor's Guide for downloading the source for XFree86 and building it. You'll want to grab the `xf-4_2-branch' of the source code. I think you would do that with: cvs checkout -r xf-4_2-branch xc Notice that some of the patches to the latest Xxserv package were not applied to the xf-4_2-branch (I don't think Alan keeps an xf-4_2-branch tree around)
Re: KDE 2.2.2 beta1 released
Hi, I hate to chime in with a me too, but I have been experiencing the same issue. I contacted Robert Collins about the issue and he said he would look into why setup is doing that. Haven't heard from him yet though... Cheers, Nicholas --- Jonathan Fosburgh [EMAIL PROTECTED] wrote: On Fri, 17 May 2002 09:39:23 +0200 Ralf Habacker [EMAIL PROTECTED] wrote: Hi all, today the KDE 2.2.2 beta 1 is released. For further details see http://cygwin.kde.org/kde2.php Have fun ! Ralf Habacker I had this problem with the installer for 2.2.1 as well, but I was hoping it would be fixed in this one. During the installation of kdebase, I will get about half way through, and then get booged down in a series of error messages that read: warning: deleting d:\cygwin/opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig_serverencryptionconfig_servercertificate_blurb.png so I can make a directory there. After hitting OK, I get another one that reads: warning: moving directory /opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig_serverencryptionconfig_servercertificate_blurb.png out of the way. At least for 2.2.1, installing manually by extracting the archive on the command line works. And, sure enough, I have multiple copies of a directory with that name. Will proceed with manual installation for 2.2.2. -- ** Jonathan Fosburgh |Certified AIX Administrator Software Systems Spec. III |ICQ: 32742908 Communications and Computer Services|MSN: [EMAIL PROTECTED] UT MD Anderson Cancer Center|Jabber: [EMAIL PROTECTED] Houston, TX |Yahoo: jefosburgh ** __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
RE: KDE 2.2.2 beta1 released
I haven't had time to test yet. Hopefully I will this weekend... Rob -Original Message- From: Nicholas Wourms [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 10:50 PM To: Jonathan Fosburgh Cc: Ralf Habacker; Cygwin-Xfree Subject: Re: KDE 2.2.2 beta1 released Hi, I hate to chime in with a me too, but I have been experiencing the same issue. I contacted Robert Collins about the issue and he said he would look into why setup is doing that. Haven't heard from him yet though... Cheers, Nicholas --- Jonathan Fosburgh [EMAIL PROTECTED] wrote: On Fri, 17 May 2002 09:39:23 +0200 Ralf Habacker [EMAIL PROTECTED] wrote: Hi all, today the KDE 2.2.2 beta 1 is released. For further details see http://cygwin.kde.org/kde2.php Have fun ! Ralf Habacker I had this problem with the installer for 2.2.1 as well, but I was hoping it would be fixed in this one. During the installation of kdebase, I will get about half way through, and then get booged down in a series of error messages that read: warning: deleting d:\cygwin/opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig _serverencryptionconfig_servercertificate_blurb.png so I can make a directory there. After hitting OK, I get another one that reads: warning: moving directory /opt/kde2/share/doc/HTML/en/kdeprint/cupsserverconfig_servere ncryptionconfig_servercertificate_blurb.png out of the way. At least for 2.2.1, installing manually by extracting the archive on the command line works. And, sure enough, I have multiple copies of a directory with that name. Will proceed with manual installation for 2.2.2. -- ** Jonathan Fosburgh |Certified AIX Administrator Software Systems Spec. III |ICQ: 32742908 Communications and Computer Services|MSN: [EMAIL PROTECTED] UT MD Anderson Cancer Center|Jabber: [EMAIL PROTECTED] Houston, TX |Yahoo: jefosburgh ** __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
RE: building xwin packages
Harold, I noticed that make won't rebuild fonts because it is looking for executables in ../../exports/bin dir. The problem is that the executables aren't native to linux. So how are you supposed to rebuild fonts without native executables? It's a bit perplexing... Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Here is my cross compile build log so that you can see what is supposed to happen: http://www.msu.edu/~huntharo/xwin/World-cross.log.bz2 (156 KiB) Hope that helps, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nicholas Wourms Sent: Thursday, May 16, 2002 8:09 PM To: Harold Hunt Subject: RE: building xwin packages Harold, Before you go, don't forget to post the script :). Thanks in advance and have a pleasant trip! Cheers, Nicholas --- Harold Hunt [EMAIL PROTECTED] wrote: Nicholas, Is there anything different which must be done now to cross compile that wasn't included in your directions or has changed since you wrote them? I haven't done a cross compile in a couple of months now. I just deleted by Cygwin cross compiler off of my Linux machine, so I'd have to spend a bit of time to do a test cross compile right now. I'm a little strapped for time right now and we're going out of town for the weekend, so it'll have to wait until next month sometime. On the other hand, I do recall that if you do not pass the flags *exactly* as documented the build process will usually bomb at imake. You should be using the command like so (all on one line, but I wrapped it for readability): [harold@MyCrossHost std]$ make World BOOTSTRAPCFLAGS=-D__CYGWIN__ -Ulinux -DCrossCompiling=1 IMAKE_DEFINES=-D__CYGWIN__ -Ulinux World.log 21 Good luck, Harold -Original Message- From: Nicholas Wourms [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 16, 2002 12:09 PM To: Harold L Hunt Subject: Re: building xwin packages Harold, I am quite aware of the the trias involved with building Xfree (I just went trough it a few months ago on OSX ;)). Given that, I was attempting to follow the directions on in the contributor's guide regarding building Xfree. Unfortunately matters have been complicated twofold, as I am quite dissappointed with the performance of compilation on my windows machine. Therefore I was setting up a cross-compile environment on my suse 7.3 linux box per your directions. This is where I want to ask a question: Is there anything different which must be done now to crosscompile that wasn't included in your directions or has changed since you wrote them? I will follow the steps below and see if my result is different, but for some reason when I followed your directions (before you sent this mail) in the howto and double checked my process, the make process bombs out on imake.c, complaining about a imake.c:395: parse error before `1'. From what I see crosscompiling needs different defines? I'm not sure...despite that my will is strong and my desire to recompile is kindled by the desire to help in testing kde. Cheers, Nicholas --- Harold L Hunt [EMAIL PROTECTED] wrote: Nicholas, Building the XFree86 packages for Cygwin is not for the faint of heart. It takes possibly many hours (especially for first timers) and there is a lot that can go wrong. With that in mind, I'll point you to two of the three steps for building the packages, and I'll post the packaging script tonight when I am on the machine that has it. I had posted the script before but the machine it was on is no longer accessible, so I'll have to put it somewhere else. Be aware that you can start the first two steps and by the time that I post the packaging script in about 8 hours you still won't have built XFree86... 1) Follow the instructions in the Cygwin/XFree86 Contributor's Guide for downloading the source for XFree86 and building it. You'll want to grab the `xf-4_2-branch' of the source code. I think you would do that with: cvs checkout -r xf-4_2-branch xc Notice that some of the patches to the latest Xxserv package were not applied to the xf-4_2-branch (I don't think Alan keeps an xf-4_2-branch tree around) so you'll need to grab the default branch and copy the files from xc/programs/Xserver/hw/xwin/ into your 4_2 tree. The relevant steps in the Contributor's Guide are here: http://xfree86.cygwin.com/docs/cg/prog-build-native.html 2) After building XFree86 you'll need to create the XFree86 packages, which is very
Re: cygwin/xfree86 Unable to open X display after first success
Wrong mailing list. Redirected. cgf On Fri, May 17, 2002 at 05:39:30PM -0400, Dennis Hui wrote: Hi, I'm having problem with X display after first successful launch of an X application. (Prior to this I did xhost +) When I remote logged in to a remote host, I first exported the DISPLAY=host-ip:0.0 and started the X application (e.g. xclock, xeyes, or xterm). Then I quitted the application, and tried to run another X app., I got: ERROR: unable to open X display. I have trouble running any subsequent X display. I have to quit XFree86 and restart X Windows before I can start my X application again. When quitting XFree86, I get the following error message: $ xterm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 XIO: fatal IO error 113 (The connection was aborted) on X server :0.0xterm: fatal IO error 113 (The connection was aborted) or KillClient on X server :0.0 after 3002 requests (3000 known processed) with 3 events = remaining. The Cygwin/XFree86 base that I use is 4.2.0-1. Please let me know if I missed anything. Thanks, Attached is the output of cygcheck -s -v -r. Dennis Hui -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ .
