Summary: | update to openoffice-1.1.4-r1 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bernd Waibel <waebbl> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bernd Waibel
2005-04-15 13:51:09 UTC
If it fails at different points this most likely is no problem with OOo but with your hardware. Could it be that your cpu gets too hot? Or that you run out of diskspace / memory? Don't think that I ran out of memory or disk space. I have 1280 megs of RAM and the partition where I compile portage packages has 12 gig free space after the compilation stopped. I don't have special sensors, but I don't think the processor gets too hot. It's not overclocked, the case is closed and I never got any error or warning related to overheating the cpu. I'll do a memtest on the next reboot tomorrow to ensure the memory is not corrupted. I had a distributed computing client (boinc) running on the machine at the same time, but it is configured to use only one of the two virtual processors (I have hyperthreading activated). May this be a problem (although I never had problems with it before. It was running on all the other OOo updates as well)? Thanks for your lighting fast answer :) Everything might be a problem if you try to build OOo, it is a very sensible beast ;) But generally, if the build fails at different points, it most likely is not the fault of OOo... Take a look at bug #20600. It gives various probable causes for compilation failure. Good chance you're suffering from one of them. It compiled successfully today. I ran memtest after boot, but it found no errors, after this it compiled. But I didn't run the distributed client at the same time, so processor load might be lower than before. Strange, as something never happens before. Much thanks for your help and hints to bug 20600 :) This is solved for me. Ok, thanks for reporting back, closing this |