Please mark =sys-devel/gcc-3.4.5 ~amd64, because it compiles and works fine (now). Reproducible: Always Steps to Reproduce: Actual Results: =sys-devel/gcc -* in package.keywords Expected Results: Nothing in package.keywords Portage 2.0.53 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r1, 2.6.14-gentoo-r4-david x86_64) ================================================================= System uname: 2.6.14-gentoo-r4-david x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre11 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.ynet.sk/pub http://ftp.du.se/pub/os/gentoo http://gentoo.osuosl.org/" LANG="cs_CZ.UTF-8" LC_ALL="cs_CZ.UTF-8" LINGUAS="cs" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aalib acpi adns alsa apache2 apm audiofile avi bash-completion berkdb bitmap-fonts bzip2 caps cdparanoia cdr cups curl curlwrappers dbus dga dio directfb divx4linux dts dvd dvdr dvdread emboss emul-linux-86 encode exif fbcon ffmpeg flac flash foomaticdb fortran ftp gd gdbm gif gpm gstreamer gtk gtk2 hal icq id3 id3v2 imagemagick imlib innodb ipv6 jabber javascript jpeg kde kdeenablefinal lcms libcaca libwww lm_sensors lzw lzw-tiff mad matroska mbox mikmod mime ming mng mp3 mpeg mplayer mysql mysqli ncurses nls nowebdav nptl nptlonly nvidia ogg oggvorbis openal opengl osc oscar pcntl pcre pdflib perl php pic png posix ppds python qt quicktime readline real recode sdl session skey slang slp sockets sox speex sqlite ssl svg symlink tcpd theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales utf8 vcd vorbis wmf xine xml xml2 xpm xv xvid zlib linguas_cs userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS
We keyword toolchain ebuilds when they are ready.
Oops... and when I usin' it now, when it isn't ready? Can it break my system? Hm, the same they've said me when I want testing =glibc-2.3.6-r1, but it works fine. :-) I'll be testing it a waiting for keyword. :-)
(In reply to comment #2) > Oops... and when I usin' it now, when it isn't ready? Can it break my system? I've said we *keyword* toolchain ebuilds when they are ready... If it breaks your system, then don't complain - it's keyworded -* ;p
Now you can ~keyword it. :-) All compiles OK with it. Including new kdelibs. :)
gcc-3.4.5 have now ~amd64 keyword... closing this bug