sys-power:phc-intel-0.3.2.12.21:20160815-072154.log

sys-power:phc-intel-0.3.2.12.21:20160815-072154.log (text/plain), 3.49 KB, created by Toralf Förster on 2016-08-15 07:32:24 UTC

 * Package:    sys-power/phc-intel-0.3.2.12.21
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/4.7.0-hardened/build
 * Found sources for kernel version:
 *     4.7.0-hardened
 * Your kernel version is not yet tested with this version of phc-intel.
 * It might not build or expose runtime problems.
 * Checking for suitable kernel configuration options...
 *   CONFIG_X86_ACPI_CPUFREQ has to be configured to Module to enable the replacement of acpi-cpufreq with phc-intel.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
>>> Unpacking source...
>>> Unpacking phc-intel-pack-rev21.tar.bz2 to /var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/work
>>> Source unpacked in /var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/work
>>> Preparing source in /var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/work/phc-intel-pack-rev21 ...
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.4.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.7.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.9.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.10.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.11.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.12.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.13.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.14.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-3.15.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-4.1.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-4.3.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-4.5.patch ...
 [ ok ]
 * Applying phc-intel-0.3.2-rev21-trailing-space-4.6.patch ...
 [ ok ]
'/usr/src/linux/drivers/cpufreq/acpi-cpufreq.c' -> './acpi-cpufreq.c'
 * Applying linux-phc-0.3.2.patch ...

 * Failed Patch: linux-phc-0.3.2.patch !
 *  ( inc/4.6/linux-phc-0.3.2.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/temp/linux-phc-0.3.2.patch.out

 * ERROR: sys-power/phc-intel-0.3.2.12.21::gentoo failed (prepare phase):
 *   Failed Patch: linux-phc-0.3.2.patch!
 * 
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 3066:  Called epatch 'inc/4.6/linux-phc-0.3.2.patch'
 *   environment, line 1019:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=sys-power/phc-intel-0.3.2.12.21::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-power/phc-intel-0.3.2.12.21::gentoo'`.
 * The complete build log is located at '/var/log/portage/sys-power:phc-intel-0.3.2.12.21:20160815-072154.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/work/phc-intel-pack-rev21'
 * S: '/var/tmp/portage/sys-power/phc-intel-0.3.2.12.21/work/phc-intel-pack-rev21'