Good - your configure finished. Start make now cd . && \ /bin/sh /var/tmp/portage/kdelibs-3.2.0_beta1/work/kdelibs-3.1.93/admin/missing --run automake-1.7 --foreign Makefile cd . && rm -f configure && make -f ./admin/Makefile.common configure make[1]: Entering directory `/var/tmp/portage/kdelibs-3.2.0_beta1/work/kdelibs-3.1.93' autom4te-2.57: cannot not rename autom4te.cache/traces.0t as autom4te.cache/traces.0: No such file or directory configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, configure.in: that aclocal.m4 is present in the top-level directory, configure.in: and that aclocal.m4 was recently regenerated (using aclocal). configure.in: required file `./install-sh' not found configure.in: required file `./mkinstalldirs' not found configure.in: required file `./missing' not found SUBDIRS: variable `TOPSUBDIRS' is used but `TOPSUBDIRS' is undefined make: *** [Makefile.in] Error 1 make: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.2.0_beta1/work/kdelibs-3.1.93' common problem, it seems: http://forums.gentoo.org/viewtopic.php?p=625221#625221
Created attachment 20187 [details] emerge --debug log Same problem here, here's what I get with emerge --debug. Versions used : automake: 1.7.5-r2 m4 : 1.4 autoconf : 2.57-r1
so it looks like the interim solution is to upgrade autoconf to 2.57a-r1 if you have 2.57 already
I have this problem too. autoconf 2.57a-r1 automake 1.7.8 m4 1.4-r1
looks like kde now requires autoconf-2.57a-r1 does that fix it?
Yes.
Ok. Count my report out since it is working for me now. Seems like I had autoconf 2.57a-r1 and 2.57 both installed, only with 'emerge -s' only showing one. I don't fully understand how Portage works. A couple of emerges later emerge was suddenly rebuilding its cache and then cleaning out old versions which removed the older autoconf. Now kdelibs builds correctly. Why did it do that? Is Portage trying to outsmart me? Why would I want to keep an old version when upgrading it? (And how does it work? 'autoconf' can't possibly point to more than one executable!)
If you have "noclean" set in your FEATURES in make.conf, portage won't remove old versions unless you explicitly tell it to. autoconf and automake are some tricky programs, because various programs require various versions. That said, there's actually a wrapper in /usr/bin that checks which version is needed and attempts to run it. You'll see that /usr/bin/automake isn't actually the automake program, but a script that attempts to identify which automake version to run based on what the program you're running it on will want. It's a hack, but it works most of the time. I'm still not 100% convinced that autoconf-2.57a is a requirement for this version of KDE, but I can't seem to find anyone that can build it with anything else. *shrug*
Closing as FIXED. Reopen if needed.
