When compiling qemu-kvm-0.12.5-r1 via a world update I get the following errors. * CPV: app-emulation/qemu-kvm-0.12.5-r1 * REPO: gentoo * USE: aio amd64 curl elibc_glibc kernel_linux kvm-trace multilib ncurses qemu_softmmu_targets_i386 qemu_softmmu_targets_x86_64 qemu_user_targets_i386 qemu_user_targets_x86_64 userland_GNU * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.34-gentoo-r1/build * Found sources for kernel version: * 2.6.34-gentoo-r1 >>> Unpacking source... >>> Unpacking qemu-kvm-0.12.5.tar.gz to /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work >>> Unpacking qemu-kvm-0.12.5-backports-1.tar.bz2 to /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work >>> Source unpacked in /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work >>> Preparing source in /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work/qemu-kvm-0.12.5 ... * Applying qemu-0.11.0-mips64-user-fix.patch ... [ ok ] * Applying qemu-kvm-0.12.3-fix-crash-with-sdl.patch ... [ ok ] * Applying qemu-kvm-0.12.3-include-madvise-defines.patch ... [ ok ] * Applying various patches (bugfixes/updates) ... * 0001-ide-Make-PIIX-and-ISA-IDE-init-functions-return-the-.patch ... [ ok ] * 0002-pc-Fix-CMOS-info-for-drives-defined-with-device.patch ... [ ok ] * Done with patching >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work/qemu-kvm-0.12.5 ... * Building the following softmmu targets: i386-softmmu x86_64-softmmu * Building the following user targets: i386-linux-user x86_64-linux-user ERROR: unknown option --disable-brltty [...] NOTE: The object files are built at the place where configure is launched * ERROR: app-emulation/qemu-kvm-0.12.5-r1 failed: * configure failed * * Call stack: * ebuild.sh, line 54: Called src_configure * environment, line 3571: Called die * The specific snippet of code: * ./configure --prefix=/usr --disable-strip --enable-kvm --enable-nptl --enable-uuid ${conf_opts} --audio-drv-list="${audio_opts}" --target-list="${softmmu_targets} ${user_targets}" --cc="$(tc-getCC)" --host-cc="$(tc-getBUILD_CC)" || die "configure failed" * * If you need support, post the output of 'emerge --info =app-emulation/qemu-kvm-0.12.5-r1', * the complete build log and the output of 'emerge -pqv =app-emulation/qemu-kvm-0.12.5-r1'. * The complete build log is located at '/var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/temp/environment'. * S: '/var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/work/qemu-kvm-0.12.5' /var/tmp/portage/app-emulation/qemu-kvm-0.12.5-r1/temp/build.log lines 91-143/143 (END) Reproducible: Always Steps to Reproduce: 1. Run 'emerge --update --deep world -v' with qemu-kvm-0.12.5 installed 2. 3. Actual Results: I received the error stated above Expected Results: It should have configured the source and begun the compilation $ uname -a Linux colossus 2.6.34-gentoo-r1 #2 SMP Tue Jul 27 19:51:17 BST 2010 x86_64 Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz GenuineIntel GNU/Linux $ cat /etc/make.conf CFLAGS="-O2 -pipe" CXXFLAGS="-O2 -pipe" CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -msse4 -mcx16 -msahf -O2 -pipe" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j9" # These settings were set by the catalyst build script that automatically # built this stage. # Please consult /usr/share/portage/config/make.conf.example for a more # detailed example. # WARNING: Changing your CHOST is not something that should be done lightly. # Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing. # These are the USE flags that were used in addition to what is provided by the # profile used for building. USE="mmx sse sse2 sse3 ssse3 sse4 -X -gnome -kde -qt3 -qt4 -ipv6 lzo lvm device-mapper" ACCEPT_LICENSE="*" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" PORTDIR_OVERLAY="/usr/local/portage"
Sorry for the spam, just spotted this is a dupe... *** This bug has been marked as a duplicate of bug 336162 ***
