* Package:    media-libs/mesa-10.4.4
 * Repository: gentoo
 * Maintainer: x11@gentoo.org
 * USE:        abi_x86_32 abi_x86_64 amd64 classic dri3 egl elibc_glibc gallium gbm kernel_linux llvm nptl udev userland_GNU video_cards_radeon
 * FEATURES:   sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking MesaLib-10.4.4.tar.bz2 to /media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/work
>>> Source unpacked in /media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/work
>>> Preparing source in /media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/work/Mesa-10.4.4 ...
 * Applying mesa-10.3.7-dont-use-clrsb.patch ...

 * Failed Patch: mesa-10.3.7-dont-use-clrsb.patch !
 *  ( /usr/portage/media-libs/mesa/files/mesa-10.3.7-dont-use-clrsb.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/temp/mesa-10.3.7-dont-use-clrsb.patch.out

 * ERROR: media-libs/mesa-10.4.4::gentoo failed (prepare phase):
 *   Failed Patch: mesa-10.3.7-dont-use-clrsb.patch!
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 4917:  Called epatch '/usr/portage/media-libs/mesa/files/mesa-10.3.7-dont-use-clrsb.patch'
 *   environment, line 2100:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * 
 * If you need support, post the output of `emerge --info '=media-libs/mesa-10.4.4::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=media-libs/mesa-10.4.4::gentoo'`.
 * The complete build log is located at '/var/log/portage/media-libs:mesa-10.4.4:20150210-145618.log'.
 * The ebuild environment file is located at '/media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/temp/environment'.
 * Working directory: '/media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/work/Mesa-10.4.4'
 * S: '/media/tmp/tmpfs/portage/media-libs/mesa-10.4.4/work/Mesa-10.4.4'