>>> Emerging (2 of 3) dev-libs/gnome-build-0.3.0 * gnome-build-0.3.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * * ERROR: dev-libs/gnome-build-0.3.0 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * gnome-build-0.3.0.ebuild, line 35: Called built_with_use 'dev-libs/gdl' 'gnome' * eutils.eclass, line 1740: Called die * The specific snippet of code: * die) die "$PKG does not actually support the $1 USE flag!";; * The die message: * dev-libs/gdl-2.24.0 does not actually support the gnome USE flag! * This is strange, and apparently the message is in error. I get the same message whether or not I use the gnome USE flag in building dev-libs/gdl, which uses only the doc USE flag. Why should a depended ebuild care whether or not I have the gnome USE flag set?
# emerge --info Portage 2.1.6.4 (default/linux/x86/2008.0/desktop, gcc-4.1.2, glibc-2.6.1-r0,glibc-2.3.4.20040808-r1, 2.6.23-gentoo-r3 i686) ================================================================= System uname: Linux-2.6.23-gentoo-r3-i686-Intel-R-_Pentium-R-_4_CPU_2.60GHz-with-glibc2.0 Timestamp of tree: Tue, 10 Feb 2009 03:30:01 +0000 ccache version 2.4 [disabled] app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 dev-util/cmake: 2.4.8 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium4 -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://gentoo.chem.wisc.edu/gentoo/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en" LC_ALL="en_US" LDFLAGS="-Wl,-O1" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acl acpi alsa apache2 apm arts berkdb bindist bluetooth bonobo branding bzip2 cairo cdr cli cracklib crypt cups curl dbus doc dri dvd dvdr dvdread eds emboss encode esd evo fam fastcgi firefox flash foomaticdb fortran gdbm gif gimp gnome gpm gps gstreamer gtk gtkhtml hal iconv imap ipv6 isdnlog java jikes jpeg kde ldap libnotify mad maildir mcal midi mikmod motif mp3 mpeg mudflap mysql ncurses nls nptl nptlonly ogg oggvorbis opengl openmp oss pam pcre pdf perl plotutils png ppds pppd python qt qt3 qt3support qt4 quicktime readline reflection samba sasl scanner sdl seamonkey session slang slp snmp spell spl sse ssl startup-notification svg svga sysfs tcltk tcpd tetex tiff truetype unicode usb vorbis win32codecs x86 xml xml2 xorg xosd xulrunner xv zeo zlib" ALSA_CARDS="emu10k1 ice1712" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="fbdev glint i810 intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa vga via vmware voodoo" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I supposed you mixed stable and unstable package. Which version of gdl do you have.
I'm using gdl 2.24.0 which is indeed marked with KEYWORDS="~x86" in the ebuild, however emerge -s shows this as the available stable package regardless of what I have in package.keywords. I know of no other mechanism for pulling this (apparently unstable) package into the index with 'emerge -s gdl' I _did_ have to pull in a substantial list of unstable packages into an update yesterday (notably various dev-python packages) in order to keep various components from trying to pull mozilla-firefox back to 2.0.0.19, and since mozilla-firefox isn't slotable, I didn't have a lot of choice unless I wanted to backversion firefox. This _did_ include dev-libs/gdl, but I tried commenting it out of package.keywords and it seems to make no difference whether I have it listed there or not. Portage thinks that gdl-2.24.0 is stable even though though the ebuild says its not. Could this be something new in the profile? Puzzled ....
(In reply to comment #3) > I'm using gdl 2.24.0 which is indeed marked with KEYWORDS="~x86" in the ebuild, > however emerge -s shows this as the available stable package regardless of what > I have in package.keywords. I know of no other mechanism for pulling this > (apparently unstable) package into the index with 'emerge -s gdl' And for the record, in case anyone has any doubt, $ACCEPT_KEYWORDS is _not_ set. As we say here in Texas, I didn't just fall off the turnip truck ;)
hu sorry for not getting back to you earlier. Your problem is that gdl-2.24 is quite a change wrt to previous versions. You need a newer gnome-build if you want to keep gdl-2.24, namely 2.24.1 since it doesn't depend on gdl anymore. Adding a blocker here would be nonsense imho because those packages are mostly used by anjuta and meant to be mostly in sync with each other which would result in a blocker nightmare. Closing invalid.
(In reply to comment #3) > I'm using gdl 2.24.0 which is indeed marked with KEYWORDS="~x86" in the ebuild, > however emerge -s shows this as the available stable package regardless of what > I have in package.keywords. I know of no other mechanism for pulling this > (apparently unstable) package into the index with 'emerge -s gdl' > > I _did_ have to pull in a substantial list of unstable packages into an update > yesterday (notably various dev-python packages) in order to keep various > components from trying to pull mozilla-firefox back to 2.0.0.19, and since > mozilla-firefox isn't slotable, I didn't have a lot of choice unless I wanted > to backversion firefox. This _did_ include dev-libs/gdl, but I tried > commenting it out of package.keywords and it seems to make no difference > whether I have it listed there or not. Portage thinks that gdl-2.24.0 is > stable even though though the ebuild says its not. Could this be something new > in the profile? > > Puzzled .... > If you used the ~X86 flag when compiling dev-libs/gdl, then you must enable the same flag to the gnome-build as well, which means to: echo "dev-libs/gnome-build ~X86" >> /etc/portage/package.keywords And then try to compile it again... The problem is, you will be using two unstable packages...
