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
2006/12/5, Richard Fish <[EMAIL PROTECTED]>:
On 12/5/06, Daniel da Veiga <[EMAIL PROTECTED]> wrote:
> On 12/5/06, Leandro Melo de Sales <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > # date
> > Tue Dec 5 10:12:01 BRT 2006
> > # emerge openoffice
> > { in other terminal }
> > # date
> > Tue Dec 5 15:24:01 BRT 2006
> >
> > and portage continues to compile openoffice, it didn't finished yet.
> > Is it so slow or there are something wrong? My machine is a P4 (with
> > HyperThreading enabled), 512Mb.
> >
>
> You may expect something between 5 and 10 hours of compilation...
/home/rjf > genlop -t openoffice
* app-office/openoffice
Mon Nov 13 01:35:33 2006 >>> app-office/openoffice-2.0.4
merge time: 2 hours, 39 minutes and 34 seconds.
Fri Nov 17 05:21:32 2006 >>> app-office/openoffice-2.0.4
merge time: 2 hours, 33 minutes and 31 seconds.
That's on an Athlon X2 4400+ with 2GB of RAM, with MAKEOPTS=-j2 and
WANT_MP=true in the environment. (Hmm, I should time this on my Core
Duo laptop also...)
But yeah, on a single-core P4 with 512MB, I'd expect on the order of
5-10 hours too. You might want to shutdown memory-consuming apps
(like X!) while the compile is running.
--
[email protected] mailing list
--
[email protected] mailing list
