RE: building xwin packages
Harold, Thanks for all your excellent help! I shouldn't have any issues now. Again, hope you have a nice trip. 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 2>&1 > > > > > > 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 yo
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
RE: building xwin packages
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 2>&1 > > > > 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 a
RE: building xwin packages
I managed to do a test cross compile for you. Everything went as planned. No build problems. I think that the crucial step you may have missed is to set the path to the Cygwin binutils and gcc executables: PATH=$PATH:/cygwin/bin:/cygwin/i686-pc-cygwin/bin I made a few updates to the Contributor's Guide. I removed a step that was irrelevant and updated the version of the binutils package. I also corrected the download directory for binutils and gcc. http://xfree86.cygwin.com/docs/cg/prog-build-cross.html So, make sure that you set the PATH correctly and try building again. Note that the host.def that I link to (which is required) does NOT build fonts by default. You will need to edit host.def and flip the NO flag for building the fonts to YES. 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 2>&1 > > > > 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
RE: building xwin packages
Nicholas, The scripts and setup.hint's are at: http://www.msu.edu/~huntharo/xwin/XFree86-cygwin-build.tar.bz2 (3 KiB) Enjoy, 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 2>&1 > > > > 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.cygwi
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 2>&1 > > 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
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 2>&1 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 it is a script, w
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 it is a script, would you post it please? > > > The reason I ask is because I want to recompile X and add it to my > local > > install directory with upset. Thanks in advance! > > > > Cheers, > > Nicholas > > > > __ > > Do You Yahoo!? > > LAUNCH - Your Yahoo! Music Experience > > http://launch.yahoo.com > > > > > __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
Re: building xwin packages
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 it is a script, would you post it please? > The reason I ask is because I want to recompile X and add it to my local > install directory with upset. Thanks in advance! > > Cheers, > Nicholas > > __ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com >
building xwin packages
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 it is a script, would you post it please? The reason I ask is because I want to recompile X and add it to my local install directory with upset. Thanks in advance! Cheers, Nicholas __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
Re: XWin doesn't always start "right"'
I, too, have forsaken the startxwin.bat startup script in favor of a home-grown script much like the one you've shown below. However, initially I ran into problems similar to what you describe. I attributed it to the fact that you can't count on the "sleep 2" command to be long enough for XWin to start. I then found that the xinit command has a way of determining that XWin is up and running before trying to launch any xclients. To use it, move most of the commands into the file ~/.xinitrc. For instance: xwinclip & python /home/geek/bin/workspace_indicator --size 200 & xv -root -maxpect -quit $HOME/images/gazebo.jpg xrdb -merge $HOME/.config/Xresources pwm Note that I left out the stuff that sets the DISPLAY to :0, xinit takes care of that for you. Also note how I moved "pwm" to the end and left it in the foreground, as per the recommendations in the xinit documentation. To run it, use this command-line: xinit -- -fullscreen -once -terminate -nowinkill -unixkill \ -auth $HOME/.Xauthority Hope this helps. >From: "Brian Gallew" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Subject: XWin doesn't always start "right"' >Date: Thu, 16 May 2002 07:24:07 -0400 (EDT) > >I'm running cygiwn/xfree on a ThinkPad under XP. Generally speaking, >the first time that I start X after booting, the window doesn't get >drawn. So, I kill it and restart X and then it works. I'm very >confused about why it behaves this way. If it matters, here's the >script I'm using to start X: >#! /bin/bash >cd /home/geek >export DISPLAY=:0 >/bin/rm -rf /tmp/.X11-unix > >run XWin -fullscreen -once -terminate -nowinkill -unixkill -auth >$HOME/.Xauthority :0sleep 2 >run xwinclip >run pwm >export DISPLAY=:0.0 >run python /home/geek/bin/workspace_indicator --size 200 >sleep 2 >xv -root -maxpect -quit $HOME/images/gazebo.jpg >xrdb -merge $HOME/.config/Xresources _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
RE: 5 seconds delay in libICE if file attributes doesn't match
> I don't know but I wonder why it is called on all platforms *except* Cygwin. > I'll look at the CVS history today. In libICE this is called on every platform, in libKDEICE, which is derived from libICE for using with DCOP, this is removed on every platform. Ralf
Re: Keyboard non us
On Thu, 16 May 2002, Uwe Schmidtmann wrote: > Hello. > > This might be a bit off this topic, but just one question: > > I am currently using xmodmap for my german keyboard. As this is working > fine (I got the map from my linux box), I would like to know if there is > any SPEED issue when using xmodmap instead of XKB? Don't know of any. xmodmap and xkb only set the scancode translation table. If it is set, the lookup is done with constant cost. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: 5 seconds delay in libICE if file attributes doesn't match
Ralf,
I don't know but I wonder why it is called on all platforms *except* Cygwin.
I'll look at the CVS history today.
Harold
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ralf Habacker
> Sent: Thursday, May 16, 2002 7:10 AM
> To: Cygwin-Xfree
> Subject: 5 seconds delay in libICE if file attributes doesn't match
>
>
> > On Thursday 16 May 2002 09:11, Ralf Habacker wrote:
> > > Hi Lubos,
> > >
> > > you have written in the kde-core-devel mailing list:
> > > > Second, this may change may help on systems which doesn't have
> > > > /tmp/.ICE-unix set to root:root 1777, where ksmserver is idle for 5
> > > > seconds, so with this change, those 5 seconds are used to
> something else.
> > >
> > > I'm porting kde 2.2.2 to cygwin/xfree and currently looking
> for places to
> > > save loading time, so this fact seems to be interesting for
> me. Because the
> > > cygwin security system does not work in all this way like
> unix (it's an
> > > emulation), this could be a significant point. I have looked into the
> > > (kde2) ksmserver sources to find the place you told about, but haven't
> > > found it. Do you have a hint for this ?
> >
> > The place is actually in libICE. You can see the change here
> > http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/dcop/KDE-ICE/Xtransut
> > il.c.diff?r1=1.3&r2=1.4
> >
> > There are actually two libICE libraries used in KDE, first one is this
> > modified version for DCOP called KDE-ICE, the second one is
> standard libICE
> > shipped with XFree86, which is used by libSM, which is used by
> ksmserver, and
> > this libICE still waits those 5 seconds when there are improper
> permissions.
> >
> Are there any reasons why this delay should be in libICE ?
>
> Is not so here is a patch
>
> Index: Xtransutil.c
> ===
> RCS file: /cvs/xc/lib/xtrans/Xtransutil.c,v
> retrieving revision 3.21
> diff -u -3 -p -B -r3.21 Xtransutil.c
> --- Xtransutil.c2001/12/14 19:57:07 3.21
> +++ Xtransutil.c2002/05/16 11:08:20
> @@ -503,12 +503,16 @@ trans_mkdir(char *path, int mode)
> if (updateOwner && !updatedOwner) {
> PRMSG(1, "mkdir: Owner of %s should be set to root\n",
> path, 0, 0);
> +#ifndef __CYGWIN__
> sleep(5);
> +#endif
> }
> if (updateMode && !updatedMode) {
> PRMSG(1, "mkdir: Mode of %s should be set to %04o\n",
> path, mode, 0);
> +#ifndef __CYGWIN__
> sleep(5);
> +#endif
> }
> return 0;
> }
>
> Regards
>
> Ralf
>
>
RE: AltGr handling from Java app on Solaris host
Arne,
I don't think anyone knows a precise answer.
Sorry,
Harold
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Arne Christian
> Hårseth
> Sent: Thursday, May 16, 2002 5:23 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: AltGr handling from Java app on Solaris host
>
>
> Hi again!
>
> I can't see I got any response so I try once more. May be I used the wrong
> address? Will try [EMAIL PROTECTED] this time.
>
> Hi!
>
> I have installed the latest Cygwin (setup say: setup-timestamp:
> 1020655814,setup-version: 2.194.2.26) and Cygwin xfree (4.2.0).
>
> I use xmodmap with the xmodmap.no found on
> http://www-usercgi.tu-chemnitz.de/~goal/index.php3?jump=xfree.
>
> Using this xmodmap the AltGr keys (which produce @£{[]}...) works fine in
> the local X bash shell. When running a remote xterm on a Solaris host the
> AltGr keys still works fine in xterm and in Emacs. When I start a Java (X)
> application (Gawors LDAP browser which can be found on
> http//www-unix.mcs.anl.gov/~gawor/ldap/index.html) on the Solaris host
> however AltGr no longer works inside the Java applications. I have tested
> the same application using XWin32 and have no problem with the AltGr key
> there.
>
> Local xev reports keycode 113 (keysym 0xff7e, Mode_swithc) when I
> press the
> AltGr key.
> I havn't found xev on the Solaris host so I don't know what that would
> report.
>
> How should I set up Cygwin xfree to handle AltGr also for Java
> applications?
>
> Arne
>
>
>
>
RE: XWin doesn't always start "right"'
Brian, I wish I knew too. Then I could fix it. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Gallew > Sent: Thursday, May 16, 2002 7:24 AM > To: [EMAIL PROTECTED] > Subject: XWin doesn't always start "right"' > > > I'm running cygiwn/xfree on a ThinkPad under XP. Generally speaking, > the first time that I start X after booting, the window doesn't get > drawn. So, I kill it and restart X and then it works. I'm very > confused about why it behaves this way. If it matters, here's the > script I'm using to start X: > #! /bin/bash > cd /home/geek > export DISPLAY=:0 > /bin/rm -rf /tmp/.X11-unix > > run XWin -fullscreen -once -terminate -nowinkill -unixkill -auth > $HOME/.Xauthority :0sleep 2 > run xwinclip > run pwm > export DISPLAY=:0.0 > run python /home/geek/bin/workspace_indicator --size 200 > sleep 2 > xv -root -maxpect -quit $HOME/images/gazebo.jpg > xrdb -merge $HOME/.config/Xresources > > >
XWin doesn't always start "right"'
I'm running cygiwn/xfree on a ThinkPad under XP. Generally speaking, the first time that I start X after booting, the window doesn't get drawn. So, I kill it and restart X and then it works. I'm very confused about why it behaves this way. If it matters, here's the script I'm using to start X: #! /bin/bash cd /home/geek export DISPLAY=:0 /bin/rm -rf /tmp/.X11-unix run XWin -fullscreen -once -terminate -nowinkill -unixkill -auth $HOME/.Xauthority :0sleep 2 run xwinclip run pwm export DISPLAY=:0.0 run python /home/geek/bin/workspace_indicator --size 200 sleep 2 xv -root -maxpect -quit $HOME/images/gazebo.jpg xrdb -merge $HOME/.config/Xresources
5 seconds delay in libICE if file attributes doesn't match
> On Thursday 16 May 2002 09:11, Ralf Habacker wrote:
> > Hi Lubos,
> >
> > you have written in the kde-core-devel mailing list:
> > > Second, this may change may help on systems which doesn't have
> > > /tmp/.ICE-unix set to root:root 1777, where ksmserver is idle for 5
> > > seconds, so with this change, those 5 seconds are used to something else.
> >
> > I'm porting kde 2.2.2 to cygwin/xfree and currently looking for places to
> > save loading time, so this fact seems to be interesting for me. Because the
> > cygwin security system does not work in all this way like unix (it's an
> > emulation), this could be a significant point. I have looked into the
> > (kde2) ksmserver sources to find the place you told about, but haven't
> > found it. Do you have a hint for this ?
>
> The place is actually in libICE. You can see the change here
> http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/dcop/KDE-ICE/Xtransut
> il.c.diff?r1=1.3&r2=1.4
>
> There are actually two libICE libraries used in KDE, first one is this
> modified version for DCOP called KDE-ICE, the second one is standard libICE
> shipped with XFree86, which is used by libSM, which is used by ksmserver, and
> this libICE still waits those 5 seconds when there are improper permissions.
>
Are there any reasons why this delay should be in libICE ?
Is not so here is a patch
Index: Xtransutil.c
===
RCS file: /cvs/xc/lib/xtrans/Xtransutil.c,v
retrieving revision 3.21
diff -u -3 -p -B -r3.21 Xtransutil.c
--- Xtransutil.c2001/12/14 19:57:07 3.21
+++ Xtransutil.c2002/05/16 11:08:20
@@ -503,12 +503,16 @@ trans_mkdir(char *path, int mode)
if (updateOwner && !updatedOwner) {
PRMSG(1, "mkdir: Owner of %s should be set to root\n",
path, 0, 0);
+#ifndef __CYGWIN__
sleep(5);
+#endif
}
if (updateMode && !updatedMode) {
PRMSG(1, "mkdir: Mode of %s should be set to %04o\n",
path, mode, 0);
+#ifndef __CYGWIN__
sleep(5);
+#endif
}
return 0;
}
Regards
Ralf
RE: Re[5]: setup.exe and inuse files for X
One thing I'm not clear on - are both calls -required-?
> -Original Message-
> From: Pavel Tsekov [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 16, 2002 8:52 PM
> To: Robert Collins
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re[5]: setup.exe and inuse files for X
>
>
> Ok, I've tested it on my WinXP Home on NTFS, FAT and FAT32.
> The following snippet removes the file no matter the
> filesystem (the Get/SetFileAttributes is required for FAT/FAT32 only):
>
> HANDLE hFile;
> DWORD dwAttr = GetFileAttributes ("test.dat");
> SetFileAttributes ("test.dat", dwAttr & ~FILE_ATTRIBUTE_READONLY);
> hFile = CreateFile ("test.dat", DELETE, 0, NULL, OPEN_EXISTING,
> FILE_FLAG_DELETE_ON_CLOSE, NULL);
> CloseHandle (hFile);
>
> RC>> Does this work on FAT too?
>
> PT> I don't know - its not clear from the documentation.
> Someone has to
> PT> test it on FAT. However this combined with an an call to
> PT> SetFileAttributes () before it should be sufficient.
>
>
Re[5]: setup.exe and inuse files for X
Ok, I've tested it on my WinXP Home on NTFS, FAT and FAT32. The
following snippet removes the file no matter the filesystem
(the Get/SetFileAttributes is required for FAT/FAT32 only):
HANDLE hFile;
DWORD dwAttr = GetFileAttributes ("test.dat");
SetFileAttributes ("test.dat", dwAttr & ~FILE_ATTRIBUTE_READONLY);
hFile = CreateFile ("test.dat", DELETE, 0, NULL, OPEN_EXISTING,
FILE_FLAG_DELETE_ON_CLOSE, NULL);
CloseHandle (hFile);
RC>> Does this work on FAT too?
PT> I don't know - its not clear from the documentation. Someone has to
PT> test it on FAT. However this combined with an an call to
PT> SetFileAttributes () before it should be sufficient.
AltGr handling from Java app on Solaris host
Hi again!
I can't see I got any response so I try once more. May be I used the wrong
address? Will try [EMAIL PROTECTED] this time.
Hi!
I have installed the latest Cygwin (setup say: setup-timestamp:
1020655814,setup-version: 2.194.2.26) and Cygwin xfree (4.2.0).
I use xmodmap with the xmodmap.no found on
http://www-usercgi.tu-chemnitz.de/~goal/index.php3?jump=xfree.
Using this xmodmap the AltGr keys (which produce @£{[]}...) works fine in
the local X bash shell. When running a remote xterm on a Solaris host the
AltGr keys still works fine in xterm and in Emacs. When I start a Java (X)
application (Gawors LDAP browser which can be found on
http//www-unix.mcs.anl.gov/~gawor/ldap/index.html) on the Solaris host
however AltGr no longer works inside the Java applications. I have tested
the same application using XWin32 and have no problem with the AltGr key
there.
Local xev reports keycode 113 (keysym 0xff7e, Mode_swithc) when I press the
AltGr key.
I havn't found xev on the Solaris host so I don't know what that would
report.
How should I set up Cygwin xfree to handle AltGr also for Java applications?
Arne
Re[4]: setup.exe and inuse files for X
Hello Robert,
Thursday, May 16, 2002, 10:59:27 AM, you wrote:
RC> Does this work on FAT too?
I don't know - its not clear from the documentation. Someone has to
test it on FAT. However this combined with an an call to
SetFileAttributes () before it should be sufficient.
Btw the snippet below is wrong - FILE_ATTRIBUTES_READONLY should be
removed from the call. I type too fast :(
>> -Original Message-
>> From: Pavel Tsekov [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, May 16, 2002 6:33 PM
RC> Ok here is how to fix this issues I've just tried it on my XP Home and
RC> it worked fine.
RC> HANDLE h = CreateFile("test.c",
RC> DELETE,
RC> 0, // We want it all :)
RC> NULL,
RC> OPEN_EXISTING,
RC> FILE_ATTRIBUTE_READONLY /*to be compatible*/
|
Bah, this here is an error --+
RC> | FILE_FLAG_DELETE_ON_CLOSE, NULL);
RC> CloseHandle (h);
RE: Re[2]: setup.exe and inuse files for X
Does this work on FAT too?
Rob
> -Original Message-
> From: Pavel Tsekov [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 16, 2002 6:33 PM
Ok here is how to fix this issues I've just tried it on my XP Home and
it worked fine.
HANDLE h = CreateFile("test.c",
DELETE,
0, // We want it all :)
NULL,
OPEN_EXISTING,
FILE_ATTRIBUTE_READONLY /*to be compatible*/
| FILE_FLAG_DELETE_ON_CLOSE, NULL);
CloseHandle (h);
Re[3]: setup.exe and inuse files for X
[snip] PT> Obviously the DELETE permission is missing. You call SetFileAttributes PT> with ~FILE_ATTRIBUTE_READONLY which shoul enable the file for reading | deleting ---+ PT> but it does not - I suppose this is why: [snip]
Re[2]: setup.exe and inuse files for X
Hello Robert,
Friday, May 03, 2002, 1:58:28 AM, you wrote:
>> -Original Message-
>> From: Corinna Vinschen [mailto:[EMAIL PROTECTED]]
>> Sent: Friday, May 03, 2002 1:44 AM
>> To: CygWin Apps; Cygwin-Xfree
>> Subject: Re: setup.exe and inuse files for X
>>
>>
>> On Wed, May 01, 2002 at 04:58:36PM +1000, Robert Collins wrote:
>> > I think I've got a handle on this... looks like read only
>> (-r--r--r--)
>> > files don't delete properly, so setup fails to overwrite them.
>> >
>> > Patches gratefully accepted, it's going in the TODO for now.
>>
>> I recall having sent a patch for this a few months ago to the
>> cygwin-apps list...
RC> Yes. And I had implemented similar code. (Including the
RC> SetFileAttributes call).
RC> I'm not sure why it is still failing to do what it should.
Check this out:
Quoted from the description of DeleteFile in the MDSN library:
To delete or rename a file, you must have either delete permission on the file
or delete child permission in the parent directory. If you set up a directory with
all access except delete and delete child and the ACLs of new files are inherited,
then you should be able to create a file without being able to delete it. However,
you can then create a file, and you will get all the access you request on the handle
returned to you at the time you create the file. If you requested delete permission
at the time you created the file, you could delete or rename the file with that handle
but not with any other.
ACL of a mode 400 file from my home directory:
C:\cygwin\home\paveltz\test.c MORDOR\paveltz:(accesso speciale:)
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
FILE_GENERIC_READ
FILE_READ_DATA
FILE_READ_EA
FILE_WRITE_EA
FILE_READ_ATTRIBUTES
FILE_WRITE_ATTRIBUTES
MORDOR\Nessuno:(accesso speciale:)
READ_CONTROL
FILE_READ_EA
FILE_READ_ATTRIBUTES
Everyone:(accesso speciale:)
READ_CONTROL
FILE_READ_EA
FILE_READ_ATTRIBUTES
Obviously the DELETE permission is missing. You call SetFileAttributes
with ~FILE_ATTRIBUTE_READONLY which shoul enable the file for reading
but it does not - I suppose this is why:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/filesio_6c8i.asp
Note that it is said:
dwFileAttributes
Specifies FAT-style attribute information for the file or directory.
But if we're on NTFS there is no joy :( I've tried a simple test with
SetFileAttributes and ~FILE_ATTRIBUTE_READONLY and it doesnt affect
the file at all.
Ok here is how to fix this issues I've just tried it on my XP Home and
it worked fine.
HANDLE h = CreateFile("test.c",
DELETE,
0, // We want it all :)
NULL,
OPEN_EXISTING,
FILE_ATTRIBUTE_READONLY /*to be compatible*/
| FILE_FLAG_DELETE_ON_CLOSE, NULL);
CloseHandle (h);
missing symbols for qt3
Hi all, the 4.2.x release of the xftlib does not export some symbols required by qt 3.x. Are there any doubts fo adding this in further xfree/cygwin releases ? Index: lib/Xft/Xft-def.cpp === RCS file: /cvs/xc/lib/Xft/Xft-def.cpp,v retrieving revision 1.2 diff -u -3 -p -B -u -b -B -p -r1.2 Xft-def.cpp --- lib/Xft/Xft-def.cpp 2001/04/05 19:29:38 1.2 +++ lib/Xft/Xft-def.cpp 2002/05/16 07:53:29 @@ -145,6 +145,12 @@ XftInitFtLibrary XftConfigDirs XftDirScan XftDirSave - +/* the next are needed by qt 3.0 */ +XftGlyphLoad +XftGlyphCheck +XftFreeTypeGlyphExists +XftFreeTypeOpen +XftFreeTypeClose +XftRenderString16 Regards Ralf
