Summary: | openoffice-2.0.3 build fails on 'project boost' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lindsay Haisley <fmouse-gentoo> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lindsay Haisley
2006-07-18 08:27:26 UTC
Well sorry, but this is not really useful, post more lines above. Jacub, how much of the build output should I post? The error occurs many minutes into a very verbose build. I've tee'd the output to a file, which has already run to over 4 megs. I can attach the whole thing, or a portion of it. This is a damned complex build and takes many hours. I'm not sure how many minutes or hours into the build (which ran overnight) the failure occurred, or how big this file will eventually become. Let me know and I'll post what's needed. Well, just some 20 lines above or so, or attach the part of the log with the error here, but we really need some context. If it fails again I'll do this, but it's about 1.5 hours into the build and still on track. Grepping the build output file indicates that it's already successfully passed "Building project boost", and so unless it fails somewhere else, or it returns to this build segment and fails, it may go to completion and we can close this bug altogether <knocking on wood!>. This smells like resource exhaustion. I know that the OO build has a reputation as a resource hog. The OO emerge went through to the end this time - all 5 hours of it :-) Since the error isn't reproduceable (my guess is that it represented a segfault caused by resource depletion) I'm closing it altogether. |