From 9c0b1c25f8f3cf0ffdc841c9eb47a81b9d4568d7 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Wed, 26 Nov 2008 18:33:28 +0000 Subject: Add some more clarification to the 'ebuild phase exited unexpectedly' message. (trunk r12101) svn path=/main/branches/2.1.6/; revision=12102 --- pym/portage/__init__.py | 17 ++++++++++++++--- 1 file 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): -- cgit v1.2.3-1-g7c22