emerge of vmware-modules-279.0 fails on the application of the 279-3-10.0.patch. Seems the patch tool isn't able to find the source files: /var/tmp/portage/app-emulation/vmware-modules-279.0/work Reproducible: Always Steps to Reproduce: 1. emerge -va vmware-modules Actual Results: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U *] app-emulation/vmware-modules-279.0 [271.2] USE="-pax_kernel" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/vmware-modules-279.0 * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.10.7-gentoo-r1/build * Found sources for kernel version: * 3.10.7-gentoo-r1 * Checking for suitable kernel configuration options... [ ok ] * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Source unpacked in /var/tmp/portage/app-emulation/vmware-modules-279.0/work >>> Preparing source in /var/tmp/portage/app-emulation/vmware-modules-279.0/work ... * Applying 279-makefile-kernel-dir.patch ... [ ok ] * Applying 279-makefile-include.patch ... [ ok ] * Applying 279-netdevice.patch ... [ ok ] * Applying 279-apic.patch ... [ ok ] * Applying 279-putname.patch ... [ ok ] * Applying 279-3.10.0.patch ... * Failed Patch: 279-3.10.0.patch ! * ( /usr/portage/app-emulation/vmware-modules/files/279-3.10.0.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/app-emulation/vmware-modules-279.0/temp/279-3.10.0.patch.out * ERROR: app-emulation/vmware-modules-279.0::gentoo failed (prepare phase): * Failed Patch: 279-3.10.0.patch! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 3579: Called epatch '/usr/portage/app-emulation/vmware-modules/files/279-3.10.0.patch' * environment, line 1391: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-279.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-279.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-279.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-279.0/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-279.0/work' * S: '/var/tmp/portage/app-emulation/vmware-modules-279.0/work' >>> Failed to emerge app-emulation/vmware-modules-279.0, Log file: >>> '/var/tmp/portage/app-emulation/vmware-modules-279.0/temp/build.log' Expected Results: Patches should have been applied. The files do exist. Linux tridmw 3.10.7-gentoo-r1 #1 SMP Thu Sep 26 11:10:08 EDT 2013 x86_64 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz GenuineIntel GNU/Linux Portage 2.2.7 (default/linux/amd64/13.0/desktop/kde, gcc-4.7.3, glibc-2.15-r3, 3.10.7-gentoo-r1 x86_64) patch 2.6.1 Copyright (C) 1988 Larry Wall Copyright (C) 2003, 2009 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of this program under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. written by Larry Wall and Paul Eggert
Created attachment 361804 [details] Patch output.
(In reply to Dave Mak from comment #1) > Created attachment 361804 [details] > Patch output. Same here.
This should be fixed now. Please open a separate bug for problems with newer kernel versions.
