1 |
On Monday 30 November 2009 00:06:23 daid kahl wrote: |
2 |
> I've been getting the same silly OpenOffice compile error for a couple |
3 |
> weeks now. Nothing I can search up or think of seems to do the trick. |
4 |
> Since it takes about 2 hours + to crash out (the *exact* same way), |
5 |
> it's also not trivial to try lots of different ideas. I'd read |
6 |
> something that suggested maybe I should update my kernel, so I got |
7 |
> around to that last week, but it doesn't change the error. |
8 |
> revdep-rebuild says the linking is fine. |
9 |
> |
10 |
> Here's the end of the output during compile: |
11 |
> |
12 |
> Making: vbaswobj.lib |
13 |
> |
14 |
> Entering |
15 |
> /var/tmp/portage/app-office/openoffice-3.1.1/work/ooo/build/ooo310-m19/sw/ |
16 |
> source/ui Making: ui1.lib |
17 |
> Making: ui2.lib |
18 |
> |
19 |
> Entering |
20 |
> /var/tmp/portage/app-office/openoffice-3.1.1/work/ooo/build/ooo310-m19/sw/ |
21 |
> util Compiling: sw/unxlngi6/misc/sw_dflt_version.c |
22 |
> Compiling: sw/unxlngi6/misc/swd_dflt_version.c |
23 |
> Compiling: sw/unxlngi6/misc/swui_dflt_version.c |
24 |
> Compiling: sw/unxlngi6/misc/msword_dflt_version.c |
25 |
> Compiling: sw/unxlngi6/misc/vbaswobj_dflt.uno_version.c |
26 |
> Compiling: sw/unxlngi6/misc/docx_dflt_version.c |
27 |
> Making: swall.lib |
28 |
> Making: swui.lib |
29 |
> Making: libswli.so |
30 |
> Making: libswdli.so |
31 |
> Making: libswuili.so |
32 |
> Making: libmswordli.so |
33 |
> Making: libvbaswobjli.uno.so |
34 |
> Making: libdocxli.so |
35 |
> Making: swen-US.res |
36 |
> Making: swja.res |
37 |
> using rsc multi-res feature |
38 |
> Module 'sw' delivered successfully. 267 files copied, 0 files unchanged |
39 |
> |
40 |
> 1 module(s): |
41 |
> unoxml |
42 |
> need(s) to be rebuilt |
43 |
|
44 |
I had hoped to never ever see this error again, looks like my hopes were |
45 |
dashed. |
46 |
|
47 |
Short answer: The OOo build system is the most fragile, spaghetti-infested |
48 |
piece of software crap ever invented, bar none. It's is worse, far worse, than |
49 |
the Windows build system. There is no easy answer. |
50 |
|
51 |
Long answer: The reason for the failure is in the build log, but it is never |
52 |
just above the error message. It is often many 1000s of lines higher. |
53 |
bugs.gentoo.org is infested with bug reports of this kind of thing, to get any |
54 |
meaningful answer you *MUST* follow the instructions in the ebuild and build |
55 |
with "MAKEOPTS=-j1", also switch off distcc and cachecc as well. |
56 |
|
57 |
|
58 |
-- |
59 |
|
60 |
|
61 |
alan dot mckinnon at gmail dot com |