/var/log/portage/elog/summary.log

file_472272.txt (text/plain), 6.57 KB, created by Tomi Salminen on 2013-06-04 10:36:21 UTC

>>> Messages generated by process 11765 on 2013-06-04 09:58:59 EEST for package sys-devel/gcc-4.8.0:

ERROR: postrm
The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
is known to be triggered by things such as failed variable assignments
(bug #190128) or bad substitution 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.
The 'postrm' phase of the 'sys-devel/gcc-4.8.0' package has failed with
exit value 1.

The problem occurred while executing the ebuild file named
'gcc-4.8.0.ebuild' located in the '/var/db/pkg/sys-devel/gcc-4.8.0'
directory. If necessary, manually remove the environment.bz2 file and/or
the ebuild file located in that directory.

Removal of the environment.bz2 file is preferred since it may allow the
removal phases to execute successfully. The ebuild will be sourced and
the eclasses from the current portage tree will be used when necessary.
Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
removal phases to be skipped entirely.

>>> Messages generated by process 11765 on 2013-06-04 09:58:59 EEST for package sys-devel/gcc-4.8.1:

WARN: setup

LTO support is still experimental and unstable.  Any bug reports
about LTO that do not include an upstream patch will be closed as
invalid.

ERROR: postinst
The ebuild phase 'postinst' has exited unexpectedly. This type of
behavior is known to be triggered by things such as failed variable
assignments (bug #190128) or bad substitution 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.
ERROR: other
The ebuild phase 'other' has exited unexpectedly. This type of behavior
is known to be triggered by things such as failed variable assignments
(bug #190128) or bad substitution 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.
QA: other
QA Notice: Package triggers severe warnings which indicate that it
           may exhibit random runtime failures.
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
/var/tmp/portage/sys-devel/gcc-4.8.1/work/gcc-4.8.1/libgcc/crtstuff.c:463:19: warning: array subscript is above array bounds [-Warray-bounds]
Please do not file a Gentoo bug and instead report the above QA
issues directly to the upstream developers of this software.
Homepage: http://gcc.gnu.org/