On Tue, 27 May 2014 20:58:56 -0400, Hunter Jozwiak wrote: Can you fix whatever you are using to post this. Portage output is difficult enough to parse without you adding extra layers of obfuscation.
> * Cannot find $EPATCHSOURCE! Value for $EPATCHSOURCE is: * * > /usr/portage/media-libs/mesa/files/mesa-10.2-dont-require-llvm-fo > r-r3004patch * were mesa-10.2-dont-require-llvm-for-r3004patch > were > * ERROR: media-libs/mesa-10.2.0.rc433gentoo failed (prepare > phase): * Cannot find $EPATCHSOURCE! * * Call stack: * > ebuildddsh, line 93: Called srcprepare * environment, line 4773: > Called epatch The ebuild is trying to apply a patch but the patch file does not exist. Most patch files are included in the portage tree and occasionally a dev omits to update one. Run emerge --sync and try again. If the problem persists, file a bug at bugs.gentoo.org, after checking that no one else has already done it. -- Neil Bothwick Experience is what you get when you didn't get what you wanted.
signature.asc
Description: PGP signature
