kde-3.1.4 runs well, emerging 3..5. will end as follows: ... checking how we should treat IPv6 lookups... never do the lookup checking for libart2-config... /usr/bin/libart2-config checking for revoke(tty) in unistd.h... yes configure: error: Fast malloc is not supported on this platform (missing spinlock implementation). !!! ERROR: kde-base/kdelibs-3.1.5 failed. !!! Function kde_src_compile, Line 117, Exitcode 1 !!! died running ./configure, kde_src_compile:configure mars root # emerge info Portage 2.0.50_pre16 (default-amd64-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.6.1-gentoo) ================================================================= System uname: 2.6.1-gentoo x86_64 4 Gentoo Base System version 1.4.3.12 Autoconf: sys-devel/autoconf-2.58 Automake: sys-devel/automake-1.7.8 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-Os -pipe -funroll-all-loops" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /opt/tomcat/conf /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-Os -pipe -funroll-all-loops" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://zayra.ds.de/gentoo-portage" USE="X aalib alsa amd64 apache2 apm avi berkdb cdr crypt dvdr encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww mikmod motif mozilla mpeg multilib ncurses nls nvidia oggvorbis opengl oss pam pdflib perl png python qt quicktime readline scanner sdl slang spell ssl tcltk tcpd truetype vi vim x86 xml2 xmms xv zlib"
hmm, not sure how amd64 is set up but the fast malloc should only be happening if you have "x86" as your architecture. Is it normal for you to have both amd64 and x86 in your use flags as arches?
Ooops, sorry! Where is this coming from? Anyway, i'll check again and report back here. Thx, Jan
Scusi, it's working now. The x86 is most likely a typo and should read xfree86!? I've no other explanation...