* Package:    sys-devel/libtool-2.4.6-r3
 * Repository: gentoo
 * Maintainer: base-system@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking libtool-2.4.6.tar.xz to /var/tmp/portage/sys-devel/libtool-2.4.6-r3/work
>>> Source unpacked in /var/tmp/portage/sys-devel/libtool-2.4.6-r3/work
>>> Preparing source in /var/tmp/portage/sys-devel/libtool-2.4.6-r3/work/libtool-2.4.6 ...
 * Applying libtool-2.4.3-use-linux-version-in-fbsd.patch ...
 [ ok ]
 * Applying libtool-2.4.6-link-specs.patch ...

 * A dry-run of patch command succeeded, but actually
 * applying the patch failed!

 * Failed Patch: libtool-2.4.6-link-specs.patch !
 *  ( /var/tmp/portage/sys-devel/libtool-2.4.6-r3/files/libtool-2.4.6-link-specs.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-devel/libtool-2.4.6-r3/temp/libtool-2.4.6-link-specs.patch.out

 * ERROR: sys-devel/libtool-2.4.6-r3::gentoo failed (prepare phase):
 *   Failed Patch: libtool-2.4.6-link-specs.patch!
 * 
 * Call stack:
 *     ebuild.sh, line  115:  Called src_prepare
 *   environment, line 2395:  Called epatch '/var/tmp/portage/sys-devel/libtool-2.4.6-r3/files/libtool-2.4.6-link-specs.patch'
 *   environment, line 1142:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/libtool-2.4.6-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/libtool-2.4.6-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/libtool-2.4.6-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.4.6-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/libtool-2.4.6-r3/work/libtool-2.4.6'
 * S: '/var/tmp/portage/sys-devel/libtool-2.4.6-r3/work/libtool-2.4.6'