cyrus-sasl-2.1.25-r4-build.log

cyrus-sasl-2.1.25-r4-build.log (text/plain), 6.44 KB, created by iGentoo on 2013-02-01 07:16:24 UTC

 * Package:    dev-libs/cyrus-sasl-2.1.25-r4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        amd64 elibc_glibc gdbm kernel_linux multilib pam selinux ssl test urandom userland_GNU
 * FEATURES:   compressdebug preserve-libs sandbox selinux sesandbox splitdebug test userpriv usersandbox
 * Package:    dev-libs/cyrus-sasl-2.1.25-r4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        amd64 elibc_glibc gdbm kernel_linux multilib pam selinux ssl test urandom userland_GNU
 * FEATURES:   compressdebug preserve-libs sandbox selinux sesandbox splitdebug test userpriv usersandbox
>>> Unpacking source...
>>> Unpacking cyrus-sasl-2.1.25.tar.gz to /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work
>>> Source unpacked in /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work
>>> Preparing source in /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25 ...
 * Applying cyrus-sasl-2.1.25-sasldb_al.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-saslauthd_libtool.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-avoid_pic_overwrite.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-autotools_fixes.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-as_needed.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-missing_header.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-gssapi.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-lib_before_plugin.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-fix_heimdal.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-auxprop.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.23-gss_c_nt_hostbased_service.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.23+db-5.0.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-get_fqhostname.patch ...
 [ ok ]
 * Applying cyrus-sasl-2.1.25-service_keytabs.patch ...
 [ ok ]
 * Running eautoreconf in '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25' ...
 * Running eautoreconf in '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/saslauthd' ...
 * Running libtoolize --install --copy --force --automake ...
 * Running libtoolize --install --copy --force --automake ...
 [ ok ]
 * Running aclocal -I /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/cmulocal -I /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/config -I cmulocal -I config ...
 [ ok ]
 * Running aclocal -I /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/cmulocal -I /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/config -I ../cmulocal -I ../config ...
 [ !! ]

 * Failed Running aclocal !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/aclocal.out

 * ERROR: dev-libs/cyrus-sasl-2.1.25-r4 failed (prepare phase):
 *   Failed Running aclocal !
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 5187:  Called eautoreconf
 *   environment, line 1221:  Called eaclocal
 *   environment, line 1021:  Called autotools_run_tool '--at-m4flags' 'aclocal' '-I' 'cmulocal' '-I' 'config'
 *   environment, line  757:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/cyrus-sasl-2.1.25-r4'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/cyrus-sasl-2.1.25-r4'`.
 * This ebuild used the following eclasses from overlays:
 *   /usr/local/portage/eclass/toolchain-funcs.eclass
 *   /usr/local/portage/eclass/flag-o-matic.eclass
 *   /usr/local/portage/eclass/autotools.eclass
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
/usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `Failed Running aclocal !': not a pid or valid job spec
 [ !! ]

 * Failed Running aclocal !
 * The complete build log is located at '/var/log/portage/build/dev-libs/cyrus-sasl-2.1.25-r4:20130201-070246.log'.
 * 
 * Include in your bugreport the contents of:
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/build.log'.
 * 
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/environment'.
 *   /var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/aclocal-1.out

 * ERROR: dev-libs/cyrus-sasl-2.1.25-r4 failed (prepare phase):
 * Working directory: '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25'
 *   Failed Running aclocal !
 * S: '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25'
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 5187:  Called eautoreconf
 *   environment, line 1190:  Called multijob_child_init 'eautoreconf'
 *   environment, line 4497:  Called eautoreconf
 *   environment, line 1221:  Called eaclocal
 *   environment, line 1021:  Called autotools_run_tool '--at-m4flags' 'aclocal' '-I' '../cmulocal' '-I' '../config'
 *   environment, line  757:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of `emerge --info '=dev-libs/cyrus-sasl-2.1.25-r4'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/cyrus-sasl-2.1.25-r4'`.
 * This ebuild used the following eclasses from overlays:
 *   /usr/local/portage/eclass/toolchain-funcs.eclass
 *   /usr/local/portage/eclass/flag-o-matic.eclass
 *   /usr/local/portage/eclass/autotools.eclass
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
/usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `Failed Running aclocal !': not a pid or valid job spec
 * The complete build log is located at '/var/log/portage/build/dev-libs/cyrus-sasl-2.1.25-r4:20130201-070246.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25/saslauthd'
 * S: '/var/tmp/portage/dev-libs/cyrus-sasl-2.1.25-r4/work/cyrus-sasl-2.1.25'
/usr/lib64/portage/bin/isolated-functions.sh: line 245: kill: (18074) - No such process