* You have both the 'gdbm' and 'berkdb' USE flags enabled.
 * Will default to GNU DB as your SASLdb database backend.
 * If you want to build with BerkeleyDB support, hit Control-C now,
 * change your USE flags -gdbm and emerge again.

 * Waiting 10 seconds before starting ...
 * (Control-C to abort) ...
>>> Unpacking source...
>>> Unpacking cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz to /var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/work
>>> Unpacking cyrus-sasl-2.1.23.tar.gz to /var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/work
 * Applying cyrus-sasl-2.1.17-pgsql-include.patch ...
  [ ok ]
 * Applying cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz ...

 * Failed Patch: cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz !
 *  ( /var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/temp/13724.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/temp/cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz-13724.out

 * 
 * ERROR: dev-libs/cyrus-sasl-2.1.23 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 4950:  Called epatch '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/distdir/cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz'
 *             environment, line 2064:  Called die
 * The specific snippet of code:
 *                   die "Failed Patch: ${patchname}!";
 *  The die message:
 *   Failed Patch: cyrus-sasl-2.1.22-ntlm_impl-spnego.patch.gz!
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.23/temp/environment'.
 * 
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/home/dkarasik/.gentoo/java-config-2/current-user-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info