summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2008-11-26 18:33:28 +0000
committerZac Medico <zmedico@gentoo.org>2008-11-26 18:33:28 +0000
commit9c0b1c25f8f3cf0ffdc841c9eb47a81b9d4568d7 (patch)
treed440ead45ae329edcf2b27ef31c3b0aca3950b1b
parent39b9c1ee0ec8a67c469d024f7248f8d1e71425cb (diff)
downloadportage-9c0b1c25f8f3cf0ffdc841c9eb47a81b9d4568d7.tar.gz
portage-9c0b1c25f8f3cf0ffdc841c9eb47a81b9d4568d7.tar.bz2
portage-9c0b1c25f8f3cf0ffdc841c9eb47a81b9d4568d7.zip
Add some more clarification to the 'ebuild phase exited unexpectedly' message.
(trunk r12101) svn path=/main/branches/2.1.6/; revision=12102
-rw-r--r--pym/portage/__init__.py17
1 files changed, 14 insertions, 3 deletions
diff --git a/pym/portage/__init__.py b/pym/portage/__init__.py
index 0df36a56b..186363235 100644
--- a/pym/portage/__init__.py
+++ b/pym/portage/__init__.py
@@ -5132,9 +5132,20 @@ def _doebuild_exit_status_check(mydo, settings):
"is known to be triggered " + \
"by things such as failed variable " + \
"assignments (bug #190128) or bad substitution " + \
- "errors (bug #200313). This behavior may also be " + \
- "triggered by a corrupt bash binary or a hardware " + \
- "problem such as memory or cpu malfunction."
+ "errors (bug #200313). Normally, before exiting, bash should " + \
+ "have displayed an error message above. If bash did not " + \
+ "produce an error message above, it's possible " + \
+ "that the ebuild has called `exit` when it " + \
+ "should have called `die` instead. This behavior may also " + \
+ "be triggered by a corrupt bash binary or a hardware " + \
+ "problem such as memory or cpu malfunction. If the problem is not " + \
+ "reproducible or it appears to occur randomly, then it is likely " + \
+ "to be triggered by a hardware problem. " + \
+ "If you suspect a hardware problem then you should " + \
+ "try some basic hardware diagnostics such as memtest. " + \
+ "Please do not report this as a bug unless it is consistently " + \
+ "reproducible and you are sure that your bash binary and hardware " + \
+ "are functioning properly."
return msg
def _doebuild_exit_status_check_and_log(settings, mydo, retval):