In src_unpack(), the call to ---- WANT_AUTOCONF=2.5 autoconf || die ---- fails with ---- Autom4te/Request.pm did not return a true value at /usr/share/autoconf/Autom4te/C4che.pm line 36. BEGIN failed--compilation aborted at /usr/share/autoconf/Autom4te/C4che.pm line 36. Compilation failed in require at /usr/bin/autom4te-2.59 line 39. BEGIN failed--compilation aborted at /usr/bin/autom4te-2.59 line 39. ---- Reproducible: Always Steps to Reproduce: 1. emerge gnome-desktop-2.8.1 (I am on ~x86 for Gnome stuff (handselected package.keywords) 2. dies Actual Results: emerge gnome-desktop-2.8.1 My "cure" was to change ---- WANT_AUTOCONF=2.5 autoconf || die ---- to simply ---- WANT_AUTOCONF=2.5 ---- So gnome-desktop-2.8.1 emerged fine. I have no idea why the original ebuild calles autoconf, possibly to enable that vendor info written in configure.in just before, but it fails... :-/ As a side-note: Got a QA notice: doc is missing in IUSE. kind regards, Florian Schricker
> gnome-desktop-2.8.1 emerged fine. I have no idea why the original ebuild calles autoconf, possibly to enable that vendor info written in configure.in just before Right.. so you do know why it calls autoconf then. > WANT_AUTOCONF=2.5 autoconf || die > WANT_AUTOCONF=2.5 Of course, because now you're not calling autoconf anymore. This doesn't break for me, we need to work out why it does for you. Can you please include your `emerge info`, as well attach the full build log. Thanks.
What's the output of: perl -I/usr/share/autoconf -e "use Autom4te::Request;"
my (current) emerge info: http://www.uni-koblenz.de/~eyerq/emerge.info.20041125
output of: perl -I/usr/share/autoconf -e "use Autom4te::Request ---- root # perl -I/usr/share/autoconf -e "use Autom4te::Request;" Autom4te/Request.pm did not return a true value at -e line 1. BEGIN failed--compilation aborted at -e line 1. ----
PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main /usr/local/bmg-gnome-current" hrmm, so you're using BMG stuff? what version of autoconf do you have installed? it looks like something's awry with your autoconf installation, which is nothing to do with gnome-desktop. Try remerging autoconf to start with.
Actually I haven't sync'd or merged any BMG thing in months. I once had BMG for gnome-2.5, but now I doubt there is any ebuild left installed. (Is there a way to check for any BMG ebuilds still installed?) Back to gnome-desktop. Re-emerging autoconf (sys-devel/autoconf-2.59-r5) did not help out, instead the error message is now doubled: ---- >>> Unpacking gnome-desktop-2.8.1.tar.bz2 to /var/tmp/portage/gnome-desktop-2.8.1/work Autom4te/Request.pm did not return a true value at /usr/share/autoconf/Autom4te/C4che.pm line 36. BEGIN failed--compilation aborted at /usr/share/autoconf/Autom4te/C4che.pm line 36. Compilation failed in require at /usr/bin/autom4te-2.59 line 39. BEGIN failed--compilation aborted at /usr/bin/autom4te-2.59 line 39. Autom4te/Request.pm did not return a true value at /usr/share/autoconf/Autom4te/C4che.pm line 36. BEGIN failed--compilation aborted at /usr/share/autoconf/Autom4te/C4che.pm line 36. Compilation failed in require at /usr/bin/autom4te-2.59 line 39. BEGIN failed--compilation aborted at /usr/bin/autom4te-2.59 line 39. autoreconf-2.59: /usr/bin/autoconf failed with exit status: 21 ---- Since autoconf depends on m4 (oh wonder *g), I am now going to re-emerge m4... kind regards & thanks for your interest! Florian Schricker
I went one step further and checked the whole dependency tree (emerge -pe) of autoconf and emerged some - automake is one them; and it failed. :-( ---- emerge automake [...] checking whether autoconf is installed... yes checking whether autoconf works... no configure: error: The installed version of autoconf does not work. Please check config.log for error messages before this one. ---- Wow - I'm puzzled. :-( config.log is at http://www.uni-koblenz.de/~eyerq/automake.config.log Any help very much appreciated, Florian Schricker
Any suggestions base-system guys?
Fixed, my autoconf install was a mess: /usr/share/autoconf/Autom4te/Request.pm was no regular file but a directory instead, containing some strange cvs data. Deleting it, re-emerged autoconf, everything runs fine again. Sorry for bothering... :-/ kind regards, Florian Schricker
Closing, since it was completely invalid. I should have checked my autoconf install before coming here...