emerging gtkballs version 3.0.1 (the only version for which there is currently an ebuild in portage, although there used to be a 3.0.0 that did the same thing) fails, since at the configure step it seems to enter an endless loop. I have also determined at least one other person ahs the same problem, so I'm not alone at least :) I had a look to see if I could work out what was happening and fix it but it was beyond me. Reproducible: Always Steps to Reproduce: 1. emerge gtkballs 2. 3. Actual Results: ...creating gtkballs-data/Makefile creating intl/Makefile creating po/Makefile.in creating config.h cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile cd . \ && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status creating Makefile ....... ad infinitum Expected Results: The installation of a great game onto your system theferret root # emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.6.0-test7-bk3) ================================================================= System uname: 2.6.0-test7-bk3 i686 AMD Athlon(tm) XP 3200+ Gentoo Base System version 1.4.3.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -fprefetch-loop-arrays" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -fprefetch-loop-arrays" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/ http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib alsa gdbm slang readline arts tetex aalib svga ggi tcltk guile X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt motif opengl cdr 3dnow acpi acpi4linux curl dga directfb doc fbcon gd gphoto2 imap ipv6 java javascript jikes justify mbox mmx mozilla music noqmax passfile pda php S3TC samba stencil-buffer tiff usb videos wmf xml xvid -kde -gnome -berkdb"
what version of autoconf & automake ?
automake (GNU automake) 1.4-p6 / Autoconf version 2.13
i meant what does `qpkg -I -v auto` show ? :)
sys-devel/automake-1.7.5-r2 * sys-devel/autoconf-2.57-r1 * is what is shows for me. Obvious, for me it works just fine otherwise I wouldn't have commited it to portage. ;-)
hmm, i'm getting the bug with gtkballs and r-katro ... i'll look into it here ... root@vapier 0 root # qpkg -I -v auto sys-devel/autoconf-2.57a-r1 * sys-devel/automake-1.7.8 *
sys-devel/autoconf-2.57a-r1 * sys-devel/automake-1.7.8 *
fixed in cvs the configure script for some stupid reason thought that running 'touch makefile.in' was a 'good' idea