* Package:    dev-libs/libmcrypt-2.5.8-r3
 * Repository: gentoo
 * Maintainer: robbat2@gentoo.org crypto@gentoo.org
 * USE:        amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking libmcrypt-2.5.8.tar.gz to /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work
>>> Source unpacked in /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work
>>> Preparing source in /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8 ...
 * Applying libmcrypt-2.5.8-rotate-mask.patch ...
 [ ok ]
 * Running eautoreconf in '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8' ...
 * Running eautoreconf in '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8/libltdl' ...
 * Running libtoolize --install --copy --force --automake ...
 [ ok ]
 * Running aclocal ...
 * Running libtoolize --copy --force --automake ...
 [ ok ]
 * Running autoconf ...
 [ ok ]
 [ !! ]

 * Failed Running autoconf !
 * 
 * Include in your bugreport the contents of:
 * 
 * Running aclocal ...
 *   /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/autoconf.out

 * ERROR: dev-libs/libmcrypt-2.5.8-r3::gentoo failed (prepare phase):
 *   Failed Running autoconf !
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 2944:  Called eautoreconf
 *   environment, line  823:  Called eautoconf
 *   environment, line  742:  Called autotools_run_tool '--at-m4flags' 'autoconf'
 *   environment, line  587:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/libmcrypt-2.5.8-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/libmcrypt-2.5.8-r3::gentoo'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 188: wait: `Failed Running autoconf !': не идентификатор  процесса или правильное имя задачи
 * The complete build log is located at '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8'
 * S: '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8'
 [ ok ]
 * Running autoconf ...
 [ ok ]
 * Running autoheader ...
 [ ok ]
 * Running automake --add-missing --copy --foreign ...
 [ ok ]

 * Messages for package dev-libs/libmcrypt-2.5.8-r3:

 * Failed Running autoconf !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/autoconf.out
 * ERROR: dev-libs/libmcrypt-2.5.8-r3::gentoo failed (prepare phase):
 *   Failed Running autoconf !
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 2944:  Called eautoreconf
 *   environment, line  823:  Called eautoconf
 *   environment, line  742:  Called autotools_run_tool '--at-m4flags' 'autoconf'
 *   environment, line  587:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/libmcrypt-2.5.8-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/libmcrypt-2.5.8-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8'
 * S: '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8'