build.log

build.log (text/plain), 2.16 KB, created by Dennis Schridde on 2013-03-21 11:55:28 UTC

[32;01m * [39;49;00mPackage:    app-emulation/libvirt-1.0.3-r2
[32;01m * [39;49;00mRepository: gentoo
[32;01m * [39;49;00mMaintainer: [e-mail] [e-mail]
[32;01m * [39;49;00mUSE:        amd64 avahi caps elibc_glibc firewalld kernel_linux libvirtd lvm lxc macvtap nls pcap policykit python qemu udev userland_GNU vepa virt-network
[32;01m * [39;49;00mFEATURES:   compressdebug preserve-libs sandbox userpriv usersandbox
 [32;01m*[0m Determining the location of the kernel source code
 [32;01m*[0m Found kernel source directory:
 [32;01m*[0m     /usr/src/linux
 [31;01m*[0m Could not find a Makefile in the kernel source directory.
 [31;01m*[0m Please ensure that /usr/src/linux points to a complete set of Linux sources
 [33;01m*[0m Unable to calculate Linux Kernel version for build, attempting to use running version
/var/cache/portage/gentoo/eclass/linux-info.eclass: line 384: value = (3 << 16) + (5 << 8) +  : syntax error: operand expected (error token is "+  ")
[31;01m * [39;49;00mThe ebuild phase 'setup' has exited unexpectedly. This type of behavior
[31;01m * [39;49;00mis known to be triggered by things such as failed variable assignments
[31;01m * [39;49;00m(bug #190128) or bad substitution errors (bug #200313). Normally, before
[31;01m * [39;49;00mexiting, bash should have displayed an error message above. If bash did
[31;01m * [39;49;00mnot produce an error message above, it's possible that the ebuild has
[31;01m * [39;49;00mcalled `exit` when it should have called `die` instead. This behavior
[31;01m * [39;49;00mmay also be triggered by a corrupt bash binary or a hardware problem
[31;01m * [39;49;00msuch as memory or cpu malfunction. If the problem is not reproducible or
[31;01m * [39;49;00mit appears to occur randomly, then it is likely to be triggered by a
[31;01m * [39;49;00mhardware problem. If you suspect a hardware problem then you should try
[31;01m * [39;49;00msome basic hardware diagnostics such as memtest. Please do not report
[31;01m * [39;49;00mthis as a bug unless it is consistently reproducible and you are sure
[31;01m * [39;49;00mthat your bash binary and hardware are functioning properly.