[sf] ~/portage/gentoo-x86/sys-devel/binutils:ebuild binutils-2.22.ebuild prepare Appending /subvolumes/gentoo-gentoo-x86 to PORTDIR_OVERLAY... * binutils-2.22.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * binutils-2.22-patches-1.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking binutils-2.22.tar.bz2 ;-) ... [ ok ] * checking binutils-2.22-patches-1.0.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking binutils-2.22.tar.bz2 to /tmp/portage/sys-devel/binutils-2.22/work >>> Unpacking binutils-2.22-patches-1.0.tar.bz2 to /tmp/portage/sys-devel/binutils-2.22/work * Applying various patches (bugfixes/updates) ... * 03_all_binutils-2.15.92.0.2-ppc64-pie.patch ... [ ok ] * 08_all_binutils-RPATH_ENVVAR-smack.patch ... [ ok ] * 12_all_sh-targets.patch ... [ ok ] * 20_all_ld-sysroot.patch ... [ ok ] * 30_all_binutils-2.22-flexible-tests.patch ... [ ok ] * 63_all_binutils-2.22-pt-pax-flags-20111121.patch ... [ ok ] * 65_all_binutils-2.20-amd64-32bit-path.patch ... [ ok ] * 66_all_binutils-2.22-warn-textrel.patch ... * Failed Patch: 66_all_binutils-2.22-warn-textrel.patch ! * ( /tmp/portage/sys-devel/binutils-2.22/work/patch/66_all_binutils-2.22-warn-textrel.patch ) * * Include in your bugreport the contents of: * * /tmp/portage/sys-devel/binutils-2.22/temp/66_all_binutils-2.22-warn-textrel.patch.out * ERROR: sys-devel/binutils-2.22 failed (unpack phase): * Failed Patch: 66_all_binutils-2.22-warn-textrel.patch! * * Call stack: * ebuild.sh, line 56: Called src_unpack * environment, line 3299: Called toolchain-binutils_src_unpack * environment, line 4107: Called tc-binutils_apply_patches * environment, line 3444: Called epatch * environment, line 1817: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of 'emerge --info =sys-devel/binutils-2.22', * the complete build log and the output of 'emerge -pqv =sys-devel/binutils-2.22'. * The complete build log is located at '/tmp/portage/sys-devel/binutils-2.22/temp/build.log'. * The ebuild environment file is located at '/tmp/portage/sys-devel/binutils-2.22/temp/environment'. * S: '/tmp/portage/sys-devel/binutils-2.22/work/binutils-2.22' Reproducible: Always Steps to Reproduce: $ eselect profile list [8] hardened/linux/amd64 *
Using sys-devel/patch-2.5.9 here
Unpacked fine with patch-2.6.1. Confused.
same problem here at an almost stable x86 with sys-devel/patch-2.5.9.
not a big deal as it only comes up when mixing stable and unstable
However, the (stable) crossdev tool installs ~arch binutils by default, even on otherwise completely stable systems, which then fails.
"stable" cross-compiling will always trail ~arch
Diego pushed a fix raising minimal required patch version: > 23 Nov 2011; Diego E. Pettenò <flameeyes@gentoo.org> binutils-2.22.ebuild: > QA: make sure to depend on a patch(1) version that actually applies all the > patches. > > *binutils-2.22 (21 Nov 2011) Looks good enough. Closing.
*** Bug 431718 has been marked as a duplicate of this bug. ***
