Not sure what the problem is. >>> Emerging (1 of 3) media-libs/allegro-4.2.2 to / * allegro-4.2.2.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking allegro-4.2.2.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking allegro-4.2.2.tar.gz to /gentoo/tmp/portage/media-libs/allegro-4.2.2/work * Applying allegro-4.2.2-exec-stack.patch ... [ ok ] * Applying allegro-4.2.2-flags.patch ... [ ok ] * Running eautoreconf in '/gentoo/tmp/portage/media-libs/allegro-4.2.2/work/allegro-4.2.2' ... * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /gentoo/tmp/portage/media-libs/allegro-4.2.2/temp/autoconf-22221.out * * ERROR: media-libs/allegro-4.2.2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2569: Called eautoreconf * environment, line 876: Called eautoconf * environment, line 819: Called autotools_run_tool 'autoconf' * environment, line 372: 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 '/var/log/portage/media-libs:allegro-4.2.2:20080418-035658.log'. * The ebuild environment file is located at '/gentoo/tmp/portage/media-libs/allegro-4.2.2/temp/environment'. *
Created attachment 150126 [details] autoconf output
Created attachment 150127 [details] emerge --info
*** Bug 219724 has been marked as a duplicate of this bug. ***
I'm hitting this one as well, amd64 system, exact same autoconf-xxxx.out file contents.
Please attach the configure file from the build directory so I can see where it went off the rails.
Created attachment 153967 [details] configure As requested: configure
Created attachment 153973 [details] aclocal.m4 Line 196 is: AC_MSG_CHECKING(for System V sys/procfs) It's not inside a function. Is that allowed?
try replacing that line with: AC_MSG_CHECKING([for System V sys/procfs]) and see if it works better.
WORKAROUND: Since this probably won't be fixed until autoconf-2.62 goes stable, those having problems (like I did) with this package may just mask autoconf-2.62, then allegro compiles just fine with the previous version. (for reference, I'm on amd64 too)
Fixed in allegro-4.2.2-r1, thanks.