tar: gcc-4.5.3/gcc/config/vax/vax-protos.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/netbsd.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/t-linux: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/netbsd-elf.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/elf.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/lib1funcs.asm: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/vax.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/openbsd1.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/constraints.md: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/predicates.md: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/builtins.md: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/vax.opt: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/vax-modes.def: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/linux.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/vax.c: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/vax.md: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/vax/openbsd.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/config/kopensolaris-gnu.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/config/memcmp.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/config/openbsd.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/config/rtems.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/tree-dump.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/tree-parloops.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/tree-ssa-loop-ivcanon.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/gthr-gnat.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/cselib.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/ddg.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/dwarf2out.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/mips-tfile.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/vec.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/collect2.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/loop-iv.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/objcp: Cannot mkdir: No space left on device
tar: gcc-4.5.3/gcc/objcp/objcp-decl.c: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/config-lang.in: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/lang-specs.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/ChangeLog: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/objcp-lang.c: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/Make-lang.in: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/objcp/objcp-decl.h: Cannot open: No such file or directory
tar: gcc-4.5.3/gcc/alias.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/store-motion.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/cif-code.def: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/omega.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/dbgcnt.def: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/crtstuff.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/hwint.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/ipa-prop.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/hooks.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/graphds.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/graphite.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/tree-flow.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/recog.h: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/plugin.def: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/tree-ssa-phiprop.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/gsstruct.def: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/combine.c: Cannot open: No space left on device
tar: gcc-4.5.3/gcc/input.h: Cannot open: No space left on device
tar: gcc-4.5.3/ltsugar.m4: Cannot open: No space left on device
tar: Exiting with failure status due to previous errors
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* ERROR: sys-devel/gcc-4.5.3-r1 failed (unpack phase):
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* failure unpacking gcc-4.5.3.tar.bz2
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
*
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* Call stack:
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* ebuild.sh, line 56: Called src_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* environment, line 4589: Called toolchain_src_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* environment, line 5402: Called gcc_quick_unpack
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* environment, line 2823: Called unpack 'gcc-4.5.3.tar.bz2'
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* ebuild.sh, line 401: Called _unpack_tar 'bzip2 -d'
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* ebuild.sh, line 371: Called assert_sigpipe_ok 'failure unpacking gcc-4.5.3.tar.bz2'
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* isolated-functions.sh, line 37: Called die
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* The specific snippet of code:
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
*
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.5.3-r1',
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.5.3-r1'.
/usr/lib/portage/bin/isolated-functions.sh: line 211: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'.
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'.
/usr/lib/portage/bin/isolated-functions.sh: line 264: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/logging/unpack: No space left on device
* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3'
Traceback (most recent call last):
File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in <module>
sys.exit(ebuild_ipc_main(sys.argv[1:]))
File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
return ebuild_ipc.communicate(args)
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock'
* The ebuild phase 'unpack' 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.
/usr/lib/portage/bin/misc-functions.sh: line 978: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/.die_hooks: No space left on device
Traceback (most recent call last):
File "/usr/lib/portage/bin/ebuild-ipc.py", line 276, in <module>
sys.exit(ebuild_ipc_main(sys.argv[1:]))
File "/usr/lib/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
return ebuild_ipc.communicate(args)
File "/usr/lib/portage/bin/ebuild-ipc.py", line 63, in communicate
lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
File "/usr/lib/portage/pym/portage/locks.py", line 73, in lockfile
myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
File "/usr/lib/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 28] No space left on device: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/.ipc_lock'
* The ebuild phase 'die_hooks' 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.
* Messages for package sys-kernel/linux-headers-2.6.36.1:
* Note: Even though you have successfully unmerged
* your kernel package, directories in kernel source location:
* /usr/src/linux-2.6.36.1
* with modified files will remain behind. By design, package managers
* will not remove these modified files and the directories they reside in.
* Messages for package sys-devel/gcc-4.5.3-r1:
* The ebuild phase 'unpack' 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.
!!! catalyst: run script failed.
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1207, in run_local
"run script failed.",env=self.env)
File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd
raise CatalystError,myexc
CatalystError
None
!!! catalyst: Stage build aborting due to error.
Traceback (most recent call last):
File "/usr/lib/catalyst/catalyst", line 209, in build_target
mytarget.run()
File "modules/generic_stage_target.py", line 1263, in run
apply(getattr(self,x))
File "modules/generic_stage_target.py", line 1212, in run_local
raise CatalystError,"Stage build aborting due to error."
CatalystError
!!! catalyst: Error encountered during run of target stage2
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage2-ia64-20111122/.catalyst_lock'
Full build log at /tmp/catalyst-auto.11232/log/stage2.log
|
