View previous topic :: View next topic |
Author |
Message |
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 2:12 pm Post subject: Time to compile kde? |
|
|
I started emerge kde this morning to get the latest version on my system. I already have xfree so it's not downloading that huge dependancy. However, the script seems to have been running for over 4 hours now on a 1.8Ghz Athlon XP processor with 256Mb and plenty of free disk space (not sure how much but there must be at least 10Gb free). I also have a broadband internet connection so download times haven't contributed a major part to the time taken.
Has anyone else experienced similar long compile times for KDE? I know it's a big package but 4 hours on a modern computer is a bit long - especially when kernel compiles take only a few minutes (or at least they did under slackware) and even xfree only took a couple of hours. How long do you think it will be before it finishes compiling? |
|
Back to top |
|
|
andrea.giusto n00b
Joined: 02 Apr 2004 Posts: 52 Location: Italy
|
Posted: Tue Apr 06, 2004 2:18 pm Post subject: |
|
|
I cant tell the exact amount of time but remember that it was very long...perhaps 5-6 hours....I did it on a Centrino 1400 512 RAM. If you dont want to wait such a long time try the --usepackage option on portage. And if you're going to compile OpenOffice, be prepared waiting even longer...I counsel to do all the compiling stuff during nighttime |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 2:22 pm Post subject: |
|
|
OpenOffice took ages to install as a binary on Fedora, so I certainly won't be compiling it from source. In fact, I don't think I need it at all - it's got bloated IMO in attempts to emulate MS office and LaTeX can be made to do all my word processing with much less effort and better results.
I don't want to use the --usepackage option because it's a bit pointless having a source-based distribution if I'm not going to compile from source - the whole reason that I chose Gentoo was to try and learn more about Linux rather than having Red Hat or another big commercial distro holding my hand every step of the way. |
|
Back to top |
|
|
andrea.giusto n00b
Joined: 02 Apr 2004 Posts: 52 Location: Italy
|
Posted: Tue Apr 06, 2004 2:35 pm Post subject: |
|
|
I agree, basically I moved to gentoo for this same reason coupled with excellent documentation, but, you know, learning is costly ...you wont be despised by kde performance. I compiled it too on my laptop and after a month of massive usage i havent yet experienced an appication crash. |
|
Back to top |
|
|
mattjgalloway l33t
Joined: 16 Mar 2004 Posts: 761 Location: Coventry, UK
|
Posted: Tue Apr 06, 2004 3:06 pm Post subject: |
|
|
KDE for me took about 8 hours to compile. That was on an Athlon 2000+ with 512mb DDR400 Ram.
Things just take a long time to compile - and as most people do, it's best to do it overnight.
Be prepared for a loooong compile _________________ AMD64 3200+, 1024MB RAM, Gentoo Linux
MacBook Core Duo, 1024MB RAM, Leopard |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 3:40 pm Post subject: |
|
|
8 hours?!? I don't know whether KDE is worth that amount of effort. I'm beginning to wish I hadn't started the thing in the first place.
Not everyone can compile overnight - my PC happens to be in my bedroom and I wouldn't be able to get to sleep with it on (apart from anything else the heat it generates is stifling if left for a long time). |
|
Back to top |
|
|
mattjgalloway l33t
Joined: 16 Mar 2004 Posts: 761 Location: Coventry, UK
|
Posted: Tue Apr 06, 2004 3:52 pm Post subject: |
|
|
Cool cool.
Mine's in my bedroom too, but i've got silent fans and stuff which make it a lot less noisy.
Yeh, you just have to stick out the compilation - it just takes time. Amuse yourself with reading or something in the meantime! _________________ AMD64 3200+, 1024MB RAM, Gentoo Linux
MacBook Core Duo, 1024MB RAM, Leopard |
|
Back to top |
|
|
jkt Retired Dev
Joined: 06 Feb 2004 Posts: 1250 Location: Prague, Czech republic, EU
|
Posted: Tue Apr 06, 2004 4:01 pm Post subject: |
|
|
btw, kde is stripped into several "suppackages" - if you `emerge -pv kde`, you'll see list of kdelibs, kdebase, kdenetwork, kdepim,... - kdebase and kdelibs (3.2.1) took each about 2 hours (don't know exactly) on athlon/1.2 with 256MB RAM. I think openoffice is worse |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 5:23 pm Post subject: |
|
|
I should have known about the other packages - emerge -p kde gave me a list but no approximation of their sizes/compile times but I've seen the list before on Slackware and Red Hat installs. Hopefully the whole process will finish in the next few hours because I don't want to keep it going much longer. |
|
Back to top |
|
|
zerojay Veteran
Joined: 09 Aug 2003 Posts: 1033
|
Posted: Tue Apr 06, 2004 7:10 pm Post subject: |
|
|
Um.. exactly how are you putting any effort into a compilation? You're just leaving the machine alone. Hell, you don't have to wait for the compile to get done to do things. I always leave my compilations going and keep doing what I was doing, listening to music, browsing the web, whatever. I'm on a much slower machine than you so you should be fine.
KDE 3.2.1 took 46 hours to compile on my PII 400 (not doing anything else). KDE 3.1.5 took 65 hours. Even with such long compile times, it's indeed worth it. |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 7:41 pm Post subject: |
|
|
I'm leaving the machine to compile because I want it to complete the job ASAP - if I start running more processes I presume that will slow the job down. I don't want it to run overnight because, as I have already said, the machine is in my bedroom and I don't want to try and get to sleep whilst it is making noise and pumping out heat. I can browse the web etc. on my laptop so that's not a problem.
Personally, I don't think KDE is worth 65 hours of compilation time - and if that's how long it will take then I won't bother.
Out of interest, what would happen if I *did* stop the compilation before it had finished, and what would be the best way to do so (Ctrl+C)? I don't want to be left with bits of KDE all over the place now that I've finally managed to get Gentoo semi-working. |
|
Back to top |
|
|
zerojay Veteran
Joined: 09 Aug 2003 Posts: 1033
|
Posted: Tue Apr 06, 2004 7:48 pm Post subject: |
|
|
It won't take anywhere near 65 hours on your box. Not even 8. |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 7:57 pm Post subject: |
|
|
It has already taken about 10 hours... |
|
Back to top |
|
|
zerojay Veteran
Joined: 09 Aug 2003 Posts: 1033
|
Posted: Tue Apr 06, 2004 8:14 pm Post subject: |
|
|
What package is it on? |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 8:21 pm Post subject: |
|
|
I have no idea, it's compiling a load of C files at the moment and that's all I can see on the screen. It has definitely done kde-base and kde-libs and I think it has done kde-pim (that's the last one I saw it downloading).
Edit: It has just started downloading pango (I think), package 46 out of 77 or something.
How can I stop this if it doesn't finish in the next hour or so? And why is it taking such a ridiculous amount of time on a fairly modern computer? |
|
Back to top |
|
|
zerojay Veteran
Joined: 09 Aug 2003 Posts: 1033
|
Posted: Tue Apr 06, 2004 8:26 pm Post subject: |
|
|
47 out of 77 - You answered your question right there. There's about 12 or 13 packages in KDE.. you're getting all the dependancies. Don't expect it to not be the same thing with Gnome either. |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 8:27 pm Post subject: |
|
|
Well how do I stop it then? It's never going to finish in time at this rate.
And I still think it is a stupidly long amount of time - packages shouldn't take longer than 10 hours to compile on modern machines, even with dependancies. |
|
Back to top |
|
|
zerojay Veteran
Joined: 09 Aug 2003 Posts: 1033
|
Posted: Tue Apr 06, 2004 8:31 pm Post subject: |
|
|
Heh.. you've got no patience. |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 8:35 pm Post subject: |
|
|
I do have patience - but it doesn't usually extend to staring at a black and white console for over 10 hours waiting for a program to compile. I also want the job to finish before I turn in for the night. |
|
Back to top |
|
|
Athas Guru
Joined: 04 Sep 2003 Posts: 394 Location: Brøndby, Denmark
|
|
Back to top |
|
|
shm Advocate
Joined: 09 Dec 2002 Posts: 2380 Location: Atlanta, Universe
|
Posted: Tue Apr 06, 2004 10:13 pm Post subject: |
|
|
this thread gets posted every five days.. perhaps we should just have a kde-bin ebuild like the openoffice-bin ebuild |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 10:19 pm Post subject: |
|
|
Athas wrote: | Pango is related to GTK, so you may be emerging the better part of GNOME too, I think. What's in your USE-flags? |
I don't know - I think this time I left them as the defaults. GTK has been downloaded and compiled so far now, but the process as a whole is still going... |
|
Back to top |
|
|
shm Advocate
Joined: 09 Dec 2002 Posts: 2380 Location: Atlanta, Universe
|
Posted: Tue Apr 06, 2004 10:22 pm Post subject: Re: Time to compile kde? |
|
|
pwaring wrote: | especially when kernel compiles take only a few minutes (or at least they did under slackware) and even xfree only took a couple of hours. How long do you think it will be before it finishes compiling? |
You can't make such comparisons, since the kernel and xfree are in C, not in C++. g++ is hideously slow compared to gcc or most c++ compilers (e.g, Visual C++) |
|
Back to top |
|
|
pwaring Tux's lil' helper
Joined: 28 Aug 2003 Posts: 99
|
Posted: Tue Apr 06, 2004 10:29 pm Post subject: |
|
|
Slow enough to add 10 hours to the compile time?! If that's the case then someone needs to optimise g++, |
|
Back to top |
|
|
shm Advocate
Joined: 09 Dec 2002 Posts: 2380 Location: Atlanta, Universe
|
Posted: Tue Apr 06, 2004 10:35 pm Post subject: |
|
|
pwaring wrote: | Slow enough to add 10 hours to the compile time?! If that's the case then someone needs to optimise g++, |
Not exactly.. but it's probably 50% slower.
When you compile a kernel, you don't compile most of it's source. When you are emerging KDE for the first time, you are emerging a LOT of dependencies.
KDE 3.2 (if you compile all of KDE+Koffice+quanta+kdevelop) and the kernel 2.6 are quite similiar in Lines of Code (but remember that you only compile a small subset of the kernel's full LOC)..
The largest performance problem with g++ is the lack of precompiled headers. This hurts C++ compilation speed a LOT more than C compilation speed. Apple implemented precompiled headers in gcc/g++, and it is part of gcc 3.4. The next Qt and KDE releases should have full support for that since it's something many developers will eagerly want. |
|
Back to top |
|
|
|