Make fails with: Making all in xmms-kde make[2]: Entering directory `/var/tmp/portage/xmms-kde-3.1_beta1/work/xmms-kde-3.1beta1/xmms-kde' Makefile:495: *** missing separator. Stop. --snip-- The results of `emerge info': Portage 2.0.51-r14 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 Intel(R) Pentium(R) 4 CPU 2.66GHz Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 13 2005, 23:59:23)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.5, 1.9.4, 1.8.5-r2, 1.6.3, 1.7.9, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r3 virtual/os-headers: 2.4.22 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks noinfo prelink sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage-overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 alsa arts crypt cups gif ipv6 jpeg mmx mmx2 opengl pam pcre perl png readline sse ssl tiff xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS
There were some problems with autoconf stuff, I committed version 3.1 and removed the amd64 specific patch that was applied in bug 41399, and now everything seems to work fine. I don't think the patch is necessary now, see bug 45669. @eradicator or another amd64 guy: please check that everything is ok on your arch.
3.1 compiles cleanly and runs fine (I'll leave it in unstable, since it's a fresh ebuild)
I'm also having this problem with the _beta1 version. I understand it can be solved by upgrading but I just wanted to add that I do actually have it emerged at the moment so I must have been able to compile it at one point. Since then, I'm not sure what could have changed on my end, and I thought that if the Gentoo team edited committed ebuilds, there'd be a new release version (-r1, -r2, etc.) - am I wrong on this?
Sorry, my bad. I've enabled the kdeenablefinal USE flag since the last time I built it. I don't know if this would make a difference.
Compilation fixes don't create new ebuild revs, because we don't want to make users who already have the older rev installed upgrade. Only fixes affecting the installed version (in the event of a successful compilation) cause a new rev. enable-final shouldn't affect anything. If it does, that's a separate bug.
