[ebuild U ] app-emulation/virtualbox-4.2.14 [4.2.12] USE="additions alsa opengl pam qt4 -doc -extensions -headless -java -pulseaudio -python -sdk -vboxwebsrv -vnc" PYTHON_SINGLE_TARGET="-python2_7%" PYTHON_TARGETS="-python2_7%" 0 kB The ebuild apparently expects python_target[s] even when python is disabled.
>>> Emerging (1 of 14) app-emulation/virtualbox-4.2.14 * VirtualBox-4.2.14.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * virtualbox-4.2.2-patches-01.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * No Python implementation selected for the build. Please set * the PYTHON_SINGLE_TARGET variable in your make.conf to one * of the following values: * * python2_7
# emerge --info =app-emulation/virtualbox-4.2.14 Portage 2.1.12.10 (default/linux/amd64/13.0, gcc-4.7.3, glibc-2.17, 3.9.5-gentoo x86_64) ================================================================= System Settings ================================================================= System uname: Linux-3.9.5-gentoo-x86_64-Intel-R-_Xeon-R-_CPU_E5-2620_0_@_2.00GHz-with-gentoo-2.2 KiB Mem: 4033552 total, 1469948 free KiB Swap: 0 total, 0 free Timestamp of tree: Fri, 28 Jun 2013 13:30:01 +0000 ld GNU ld (GNU Binutils) 2.23.1 app-shells/bash: 4.2_p45 dev-java/java-config: 2.2.0 dev-lang/python: 2.7.5, 3.2.5, 3.3.2 dev-util/cmake: 2.8.11.1 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.13.4, 1.14 sys-devel/binutils: 2.23.1 sys-devel/gcc: 4.7.3 sys-devel/gcc-config: 1.8 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.9 (virtual/os-headers) sys-libs/glibc: 2.17 Repositories: gentoo x-local ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA dlj-1.1 PUEL AdobeFlash-11.x Oracle-BCLA-JavaSE google-chrome" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=corei7 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=corei7 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://lug.mtu.edu/gentoo/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://www.gtlib.gatech.edu/pub/gentoo" LANG="en_US" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/local" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X accessibility acpi alsa amd64 bash-completion bzip2 cddb cleartype cli cracklib crypt cups curl cxx dbus dell dri fam glib glx gtk gtk3 hal iconv java6 jpeg laptop libnotify logrotate midi mmx multilib ncurses nls nptl nptlonly nsplugin ntp opengl pam pcf pcre perl pmu png python readline session sqlite sse sse2 sse4_1 sse4_2 ssl ssse3 startup-notification svg tcpd threads tiff truetype udev unicode vaapi xcomposite xinerama xorg xrender xscreensaver xulrunner zlib" ABI_X86="64" ELIBC="glibc" GRUB_PLATFORMS="pc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LINGUAS="en_US en" PYTHON_SINGLE_TARGET="python3_2" PYTHON_TARGETS="python2_7 python3_2" USERLAND="GNU" VIDEO_CARDS="intel virtualbox" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
This cannot be fixed because the virtualbox build system requires python-2.7. The "python" USE flag only controls installation of the python bindings. I've added a warning to the ebuild when the USE flag is disabled. Is this sufficient for you?
Absolutely. Knowing why it's still needed in spite of being disabled in the build output removes the confusion.
(In reply to Leeman Strout from comment #4) > Absolutely. Knowing why it's still needed in spite of being disabled in the > build output removes the confusion. That's great. The warning was added to 4.2.14 and 4.2.16.
