When using "emerge kde" to make and install kde 3.2.0, one dependency I need is fam 2.7.0. When emerge gets to it, it goes through one configure, does some shell stuff that goes to fast to see, and then goes through another configure and afterwards goes through some mroe shell stuff and fails on running a program called "missing" in the fam-2.7.0/work directory. The output looks like this: configure: creating ./config.status cd . && /bin/sh ./config.status Makefile config.status: creating Makefile cd . && /bin/sh /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/missing --run autoheader /usr/bin/autoheader-2.58: unrecognized option `--language=autoconf' Try `/usr/bin/autoheader-2.58 --help' for more information. autoheader-2.58: /usr/bin/autoheader-2.58 failed with exit status: 1 make: *** [config.h.in] Error 1 !!! ERROR: app-admin/fam-2.7.0 failed. !!! Function src_compile, Line 418, Exitcode 2 !!! emake failed I'm not exactly sure what is going on, but after the first configure, something similar looking works fine. That looks like: config.status: executing depfiles commands cd . && /bin/sh /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/missing --run aclocal-1.6 cd . && \ /bin/sh /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/missing --run automake-1.6 --gnu Makefile cd . && /bin/sh /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/missing --run autoconf /bin/sh ./config.status --recheck running /bin/sh ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib CC=gcc CFLAGS=-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe CXXFLAGS=-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe CXX=g++ host_alias=i686-pc-linux-gnu --no-create --no-recursion
hmm is this still a problem ?
I had a different problem, also automake related. (aclocal) Solved by the dnotify enabled fam ebuild, which forces automake 1.5 (probably the trick, not verified, i want dnotify, no removable media on that machine so no issue wether that is fixed or not) The error reported in this bug is probably caused by the usage of autob0rk 1.6 ;)
have had no other bugs on this, closing