RE: building xwin packages
Not at all. I've got 256 MB of RAM, a 550 MHz PIII and a UDMA/66 hard drive (properly configured, which doesn't happen by default) on my Linux machine. I'm also using ReiserFS which was far faster than IBM's JFS and much much faster than SGI's XFS. I didn't do a test build with the default FS (I'm at a loss for the name right now) but I think it would be slower than Reiser. Anyway, build times for XFree86 depend on a lot of things and it is not unusual for it to take over an hour. Harold > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Nicholas Wourms > Sent: Friday, May 17, 2002 8:48 AM > To: Cygwin-Xfree > Subject: 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 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 > > > j
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 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. >
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 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 >
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 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
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 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
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
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
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 > > > > >
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 t
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 packag
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/
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 > > > > > > > &g
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, s
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
