1 |
On Montag, 5. Mai 2008, Wolf Canis wrote: |
2 |
> Volker Armin Hemmann wrote: |
3 |
> > On Montag, 5. Mai 2008, Wolf Canis wrote: |
4 |
> >> Volker Armin Hemmann wrote: |
5 |
> >>> extremly long. So long that you have to start ooo several times a day |
6 |
> >>> for a year so that the saved startup time equalizes the time spent |
7 |
> >>> compiling it. |
8 |
> >> |
9 |
> >> "ccache" in make.conf is enabled and MAKEOPTS has a reasonable value, I |
10 |
> >> have set it |
11 |
> >> to "-j2". I follow the rule MAKEOPTS=<number CPUS>. But in the case of |
12 |
> >> openoffice, the |
13 |
> >> ebuild overwrite this value with "-j1". For the version 2.3.x I had set |
14 |
> >> the variable |
15 |
> >> WANT_MP but with version 2.4 it breaks the build. But how you can see |
16 |
> >> in the following, |
17 |
> >> that's only a minor problem. |
18 |
> > |
19 |
> > or not. So everything bigger than -j1 breaks the built. Which makes dual |
20 |
> > core cpus useless to speed up compilation. |
21 |
> |
22 |
> Not really, because if you have set -pipe in CFLAGS than you can |
23 |
> easily, with top, check how the cpus are used. But that's it, of course. |
24 |
> |
25 |
> How I mentioned earlier with version 2.3.x I had set WANT_MP=true |
26 |
> and MAKEOPTS=-j2 (and with my first builds -j4 and -j5 but that was pretty |
27 |
> much useless, because the processes are hinder them self but they don't |
28 |
> break |
29 |
> the build) and that works for me. The only problem which occurred was this |
30 |
> |
31 |
> https://bugs.gentoo.org/show_bug.cgi?id=210065 |
32 |
> |
33 |
> >> wolf-di6400 0(0) 03:04 PM ~ # qlop -gH openoffice |
34 |
> >> openoffice: Fri May 2 16:22:23 2008: 1 hour, 20 minutes, 38 seconds |
35 |
> >> openoffice: Sat May 3 04:06:11 2008: 1 hour, 19 minutes, 12 seconds |
36 |
> >> openoffice: 2 times |
37 |
> > |
38 |
> > emerge -p openoffice-bin|genlop -p |
39 |
> > These are the pretended packages: (this may take a while; wait...) |
40 |
> > |
41 |
> > [ebuild R ] app-office/openoffice-bin-2.4.0 |
42 |
> > |
43 |
> > |
44 |
> > Estimated update time: 2 minutes. |
45 |
> |
46 |
> Yeh, of course is that faster but why we use Gentoo? Because |
47 |
> of the fast binary install? ;-) |
48 |
|
49 |
with packages that are only needed once in a while (ooo, frickelfox) binaries |
50 |
might be the right thing to do. |
51 |
|
52 |
I have compiled ooo in the past - on much, much slower machines. Ever compiled |
53 |
it on a 900mhz thunderbird? I did (and later faster cpus, of course). |
54 |
Inclusive seeing it fail after 8h because the wrong java version was |
55 |
installed. It took less time to emerge ALL of kde than ooo. And one day I |
56 |
compared the differences. ooo started maybe 3 seconds faster than ooo-bin. As |
57 |
soon as started, no difference at all. |
58 |
|
59 |
That was not worth the trouble. |
60 |
|
61 |
> Although I conduct all emerges at the console _not_ in X. Perhaps |
62 |
> that's it. However, every user should do how he/she likes. |
63 |
|
64 |
it does not matter where - ooo is huge - bloated. And whereever you emerge it, |
65 |
it is the package needing the most time. |
66 |
|
67 |
|
68 |
-- |
69 |
gentoo-user@l.g.o mailing list |