On Tuesday 05 December 2006 22:49, Leandro Melo de Sales wrote: > Ok... thanks Michael and Neil, I didn't know that compiling > openoffice take to many times. For next big emerges I'll do what you > suggested.
For future reference, there are several big packages that can take a while to compile. OpenOffice is by far the longest, some others are: - the old monolithic kde ebuilds. 8 or 9 BIG packages. The newer kde-meta ebuilds are better in this regard - 200 smaller packages - kdelibs, even as a single package, it can still be an hour on most laptops - glibc if it compiles all locales - mozilla-firefox and seamonkey. 1.5 to 2 hours is not unusual - the old monolithic X server. You shouldn't be using this anymore though - php In general, if the source package is big, then the compile will take a while. Anything over 30M of source will probably take at least an hour (give and take some of course) And screen is your second best friend ever (Google is the first). It's so useful you might consider putting it in your shell profile so you can't forget to use it alan > > Leandro > > 2006/12/5, Michael Sullivan <[EMAIL PROTECTED]>: > > On Tue, 2006-12-05 at 16:46 -0300, Leandro Melo de Sales wrote: > > > OK. The problem is that I typed "emerge openoffice" in a xterm. > > > Is it possible to turn X off and continue compilation on console? > > > > > > Leandro > > > > If you can get to your non-X console (Control+Alt+F1) and from > > there issue /etc/init.d/xdm stop. I'm not quite sure what would > > heppen to the progress you've made, since it's in an xterm. You > > should probably do big emerges like that in a screen... > > > > -- > > gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
