| 1 |
OK. The problem is that I typed "emerge openoffice" in a xterm. Is it |
| 2 |
possible to turn X off and continue compilation on console? |
| 3 |
|
| 4 |
Leandro |
| 5 |
|
| 6 |
2006/12/5, Richard Fish <bigfish@××××××××××.org>: |
| 7 |
> On 12/5/06, Daniel da Veiga <danieldaveiga@×××××.com> wrote: |
| 8 |
> > On 12/5/06, Leandro Melo de Sales <leandroal@×××××.com> wrote: |
| 9 |
> > > Hi, |
| 10 |
> > > |
| 11 |
> > > # date |
| 12 |
> > > Tue Dec 5 10:12:01 BRT 2006 |
| 13 |
> > > # emerge openoffice |
| 14 |
> > > { in other terminal } |
| 15 |
> > > # date |
| 16 |
> > > Tue Dec 5 15:24:01 BRT 2006 |
| 17 |
> > > |
| 18 |
> > > and portage continues to compile openoffice, it didn't finished yet. |
| 19 |
> > > Is it so slow or there are something wrong? My machine is a P4 (with |
| 20 |
> > > HyperThreading enabled), 512Mb. |
| 21 |
> > > |
| 22 |
> > |
| 23 |
> > You may expect something between 5 and 10 hours of compilation... |
| 24 |
> |
| 25 |
> /home/rjf > genlop -t openoffice |
| 26 |
> * app-office/openoffice |
| 27 |
> |
| 28 |
> Mon Nov 13 01:35:33 2006 >>> app-office/openoffice-2.0.4 |
| 29 |
> merge time: 2 hours, 39 minutes and 34 seconds. |
| 30 |
> |
| 31 |
> Fri Nov 17 05:21:32 2006 >>> app-office/openoffice-2.0.4 |
| 32 |
> merge time: 2 hours, 33 minutes and 31 seconds. |
| 33 |
> |
| 34 |
> That's on an Athlon X2 4400+ with 2GB of RAM, with MAKEOPTS=-j2 and |
| 35 |
> WANT_MP=true in the environment. (Hmm, I should time this on my Core |
| 36 |
> Duo laptop also...) |
| 37 |
> |
| 38 |
> But yeah, on a single-core P4 with 512MB, I'd expect on the order of |
| 39 |
> 5-10 hours too. You might want to shutdown memory-consuming apps |
| 40 |
> (like X!) while the compile is running. |
| 41 |
> -- |
| 42 |
> gentoo-user@g.o mailing list |
| 43 |
> |
| 44 |
> |
| 45 |
-- |
| 46 |
gentoo-user@g.o mailing list |
Archives