# emerge -v1 =media-video/mpeg4ip-1.5.0.1-r3 <...> * Running aclocal ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /tmp/portage/media-video/mpeg4ip-1.5.0.1-r3/temp/autoconf-32033.out * * ERROR: media-video/mpeg4ip-1.5.0.1-r3 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2582: Called eautoreconf * environment, line 848: Called eautoconf * environment, line 791: Called autotools_run_tool 'src_unpack' * environment, line 336: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running autoconf ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/tmp/portage/media-video/mpeg4ip-1.5.0.1-r3/temp/build.log'. * The ebuild environment file is located at '/tmp/portage/media-video/mpeg4ip-1.5.0.1-r3/temp/environment'. * # cat /tmp/portage/media-video/mpeg4ip-1.5.0.1-r3/temp/autoconf-32033.out ***** autoconf ***** ***** autoconf configure.in:413: error: possibly undefined macro: AM_PATH_ALSA If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:659: error: possibly undefined macro: AM_PATH_GTK_2_0 I have no gtk 2 and no alsa (this is headless server). Reproducible: Always
[ebuild U ] media-video/mpeg4ip-1.5.0.1-r3 [1.5.0.1-r1] USE="a52 aac mpeg2 x264 xvid -alsa -arts -esd -ffmpeg -id3 -ipv6 -lame (-mmx) -mp4live -nas -player -v4l2" 0 kB
This is in NO way libtool 2 related. Those macros are simply missing, cause those packages are not installed. It's simply that nobody expected this package to be installed on a system without alsa and/or gtk. I don't see a sane way to fix it, cause eautoreconf needs all macros to be provided. Though, it may be possible to patch configure.in to use pkg-config checks for those packages. I'd discourage moves like 'cp aclocal.m4 foo.m4' cause those CAN cause libtool 2 related problems.
(In reply to comment #2) > This is in NO way libtool 2 related. > Those macros are simply missing, cause > those packages are not installed. > It's simply that nobody expected this package > to be installed on a system without alsa and/or gtk. > I don't see a sane way to fix it, cause eautoreconf > needs all macros to be provided. > Though, it may be possible to patch configure.in > to use pkg-config checks for those packages. > I'd discourage moves like 'cp aclocal.m4 foo.m4' > cause those CAN cause libtool 2 related problems. Why don't just add alsa-utils and >gtk+2.0 to DEPEND?
(In reply to comment #3) > Why don't just add alsa-utils and >gtk+2.0 to DEPEND? They're already been added to -r4/-r5 ..
