Re: Just how long does it take to compile?
måndagen den 15 juli 2002 21.34 skrev John Gay: So, my question is, just how long can I expect the rest of KDE3 to take to compile? Yes, I know I can now get unstable deb's, but I want to try it for myself. The tar balls are from around Jan this year. I doubt you can do it in reasonable time with 16MB of memory. That kind of memory no one wants anymore, so you should be able to get it second hand for almost nothing, or even for free. If you have enough RAM, my guess is that you can count on a week for compilation time on your CPU. -- Karolina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
why don't you compile it on your faster hardware, and shift it over to the slower machine for install? John Gay [EMAIL PROTECTED]To: debian-kde@lists.debian.org om.net cc: Subject: Just how long does it take to compile? 15/07/02 20:34 I've been playing arould with Debain for several years now, but I've always been aware of the delay between software release and Debian release, especially when freeze is approching. I've been toying with the idea of building my own custom box for a while, and since I have some spare hardware and several source tar balls around, I decided to give it a go. Unfortunately, the box is rather old, 200Mhz Pentium MMX with 16M ram. I installed a base Debian from Woody CD's and most of the development files. Next, I compiled X4.2.0 from sources I have on CD to support my GVX1 card. Now I am in the process of compiling KDE3. I say in the process, Actually qt libs have been compiling now for over 24 hours! I did have a problem with memory limitations, and had to re-size both my root and swap partitions. I realise 16M is far too little memory, but I am hoping that if I get this box running, I can swap it for my daughters box which has 64M of the same type of memory. So, my question is, just how long can I expect the rest of KDE3 to take to compile? Yes, I know I can now get unstable deb's, but I want to try it for myself. The tar balls are from around Jan this year. Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify [EMAIL PROTECTED] This footnote also confirms that this email message has been checked for all known viruses. ** SCEE 2002 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Just how long does it take to compile?
Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) This machine takes old RAM's which should be easy and cheap to find. Unfortunately neither is the case. Shops don't carry them so second-hand is the only source. And second hand is rarer than hen's teeth since most home users have swapped these machines out ages ago. Like I said, my duaghter currently has 64M in her machine. I am hoping to prove to her that this new machine will be better then her current one, which doal-boots with Windows95 for her printer and scanner and a few games I never see her play anymore. The printer now seems to be supported, Xerox M750, but the scanner is Parallel, which might be a problem. As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? If someone can answer the two points above to my satisfaction, and remember, I'm not really a programmer, I just play one in my dreams ;-), then I might take the chance with compiling on my faster box. The wife keeps complaining about the box being on all night, often thrashing, and just how much power is it using. Thanks for the answers and suggestions. I look forward to even more, but I'm having problems with my ISP's mail service. Seems I can send mails just fine, but can't fetch them reliably? Sometimes it helps if I fetch a few of them via the web site, but that removes them from my mail box, so I risk loosing many mails that way. Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 16 July 2002 06:15 am, John Gay wrote: Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. One way is to add a new partition to your system and install a debian base, source, compiler and begin your task. A second way, and one that was fun to see on my own box, is using fakeroot, debootstrap, and chroot(?). Early versions of kde3 were compiled on this computer in this *new* environment. It actually installs a new version of Debian, in a protected environment. A user then can become a fakeroot user and apt-get all the stuff needed to build packages. I don't recall all the binaries that are needed, but I know that there is at least one hacker that does, and reads this list! 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? This is a compiler option. As far as I know, all binary packages in debian are built for a 386 (for intels). When you are ready to build, add the appropriate string and press ENTER to build for your particular needs. John Gay I hope this helps. tatah and 73 - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9NFkyZHBxKsta6kMRAnTWAKCUmgloY75nJ4We7yOAr6bxPB3JCwCgjdBD OgOobOK3ACy9zTMTSZ4j3A0= =5wsd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Just how long does it take to compile?
On Tue 16 Jul 2002 18:34, Jaye Inabnit ke6sls wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 16 July 2002 06:15 am, John Gay wrote: Well, it seems the consensus is about a week?!? Being out of work at the moment, I've got nothing but time. There have also been a few suggestions, which I'll give my answers to and maybe someone can enlighten me in the errors of my ways ;-) As for compiling on my dual PII 350 and copying over. Yes, I've got a network connection so connectivity is not an issue. The two things I am worried about are: 1) How can I compile this on my current, working KDE2 system without screwing it up. Every time I've tried playing with such things, I've alway been bitten, 999 times bitten, once shy. One way is to add a new partition to your system and install a debian base, source, compiler and begin your task. Since I've two hard drives, hda and hdb and a CD-RW and DVD in hdc and hdd, I'd have to go to SCSI drives to add any more. Also, my current disks are FULL! I really need to delete a few things ;-) A second way, and one that was fun to see on my own box, is using fakeroot, debootstrap, and chroot(?). Early versions of kde3 were compiled on this computer in this *new* environment. It actually installs a new version of Debian, in a protected environment. A user then can become a fakeroot user and apt-get all the stuff needed to build packages. I don't recall all the binaries that are needed, but I know that there is at least one hacker that does, and reads this list! This sounds more interesting, but again, I just want to build pure binaries, not deb's. I suppose I could still use the fakeroot route, but again, I'd need to free up some space. 2) As my system is PII and the target is PentiumMMX I'm not sure exactly haw to cross-compile. If I ws willing to take the plunge and upgrade MY desktop, I could compile for my PII and hopefully get a bit of performance improvement, but I would need to compile for the PentiumMMX in the target box. It seems simpler, but slower, just to compile on the target in the first place. I know(think?) that it will optimise for the Pentium rather than the 386 compatible deb's for a bit of performance? This is a compiler option. As far as I know, all binary packages in debian are built for a 386 (for intels). When you are ready to build, add the appropriate string and press ENTER to build for your particular needs. Yes, but it's also something that is checked during ./configure. So, if I'm not mistaken, when I ran ./configure, with the options I wanted, it noticed it was a PentiumMMX and set some variable in the Makefile's for this. Teh compiling seems to be set for 586 rather than 386. Of course if I had compiled this on my box, it would have been set to 686 instead. I think, for the time being, I'll just keep going on the Pentium box, since kdelibs is about 12 hours along and qtlibs took about 30 odd hours. I'll be building most of the modules, 1) because I'm a glutton for punishment. 2) I want to see them on my Daughters new box. John Gay I hope this helps. Thanks for the info. I'll probably try this out with something else in the future, like when Linux Format puts KDE3.1.0 on CD for me :-) tatah and 73 - -- Also, I've been invited to assist in testing some 3D acceleration stuff for XFree86, since one of the developers has a dodgy card. This could be great fun in itself! Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Just how long does it take to compile?
I've been playing arould with Debain for several years now, but I've always been aware of the delay between software release and Debian release, especially when freeze is approching. I've been toying with the idea of building my own custom box for a while, and since I have some spare hardware and several source tar balls around, I decided to give it a go. Unfortunately, the box is rather old, 200Mhz Pentium MMX with 16M ram. I installed a base Debian from Woody CD's and most of the development files. Next, I compiled X4.2.0 from sources I have on CD to support my GVX1 card. Now I am in the process of compiling KDE3. I say in the process, Actually qt libs have been compiling now for over 24 hours! I did have a problem with memory limitations, and had to re-size both my root and swap partitions. I realise 16M is far too little memory, but I am hoping that if I get this box running, I can swap it for my daughters box which has 64M of the same type of memory. So, my question is, just how long can I expect the rest of KDE3 to take to compile? Yes, I know I can now get unstable deb's, but I want to try it for myself. The tar balls are from around Jan this year. Cheers, John Gay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
