* Package:    dev-util/scanmem-0.17
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_single_target_python3_9 userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

>>> Unpacking source...
>>> Unpacking scanmem-0.17.tar.gz to /var/tmp/portage/dev-util/scanmem-0.17/work
>>> Source unpacked in /var/tmp/portage/dev-util/scanmem-0.17/work
>>> Preparing source in /var/tmp/portage/dev-util/scanmem-0.17/work/scanmem-0.17 ...
 * Running eautoreconf in '/var/tmp/portage/dev-util/scanmem-0.17/work/scanmem-0.17' ...
 * Running 'intltoolize --automake --copy --force' ...
 [ !! ]

 * Failed running 'intltoolize'!
 * 
 * Include in your bug report the contents of:
 * 
 *   /var/tmp/portage/dev-util/scanmem-0.17/temp/intltoolize.out

 * ERROR: dev-util/scanmem-0.17::gentoo failed (prepare phase):
 *   Failed running 'intltoolize'!
 * 
 * Call stack:
 *     ebuild.sh, line  127:  Called src_prepare
 *   environment, line 2500:  Called eautoreconf
 *   environment, line 1291:  Called autotools_run_tool 'intltoolize' '--automake' '--copy' '--force'
 *   environment, line  974:  Called die
 * The specific snippet of code:
 *           die "Failed running '${1}'!";
 * 
 * If you need support, post the output of `emerge --info '=dev-util/scanmem-0.17::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/scanmem-0.17::gentoo'`.
 * The complete build log is located at '/var/log/portage/dev-util:scanmem-0.17:20210728-042554.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-util/scanmem-0.17/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/scanmem-0.17/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/scanmem-0.17/work/scanmem-0.17'
 * S: '/var/tmp/portage/dev-util/scanmem-0.17/work/scanmem-0.17'