Testing qemu-kvm-0.14.1-r1 , initially seemed ok, but giving it the more arduous work out, could not get past the 3rd. use flag to fail a standard emerge, the straw that broke the back. Reproducible: Always Steps to Reproduce: 1. Set any of use flags debug, rbd and static for the app. 2. Emerge, stable system. 3. Actual Results: for setting use flag static; ERROR ERROR: User requested feature sdl ERROR: configure was not able to find it ERROR * ERROR: app-emulation/qemu-kvm-0.14.1-r1 failed (configure phase): * configure failed This is nonsense since the sdl flag is set, the package libsdl is emerged already and there is no occurrence of not finding the sdl flag with any other combination of set use flags. For setting use flag rbd: ERROR ERROR: User requested feature rados block device ERROR: configure was not able to find it ERROR For setting the use flag debug; --disable-spice disable spice --enable-spice enable spice --enable-rbd enable building the rados block device (rbd) NOTE: The object files are built at the place where configure is launched * ERROR: app-emulation/qemu-kvm-0.14.1-r1 failed (configure phase): * configure failed Expected Results: AN effective emerge. rbd is new to me, debug there is no excuse, and static arguably requires a specific setup.
Created attachment 275921 [details] build log for debug set
Created attachment 275923 [details] build log for rdb set
Created attachment 275925 [details] build log for static set
The failure for USE=debug looks to be because upstream uses a script called configure, but does not actually use autoconf. As a result, it does not follow the convention that the existence of --enable-FOO implies the existence of --disable-FOO. The script supports --disable-strip, but not --enable-strip, so calling $(use_enable debug strip) is inappropriate. Since the ebuild already passes a separate --disable-strip to avoid upstream pre-stripping files, the line that uses use_enable should probably be dropped, rather than modified.
(In reply to comment #4) > The failure for USE=debug looks to be because upstream uses a script called > configure, but does not actually use autoconf. As a result, it does not follow > the convention that the existence of --enable-FOO implies the existence of > --disable-FOO. The script supports --disable-strip, but not --enable-strip, so > calling $(use_enable debug strip) is inappropriate. Since the ebuild already > passes a separate --disable-strip to avoid upstream pre-stripping files, the > line that uses use_enable should probably be dropped, rather than modified. Thank you. I've also made a few other tweaks to debug flags and now USE=debug should build.
(In reply to comment #3) > Created attachment 275925 [details] > build log for static set Unfortunately with current EAPIs the depends can not be expressed for static builds. I honestly don't really see the advantage for static builds, so I've disabled them.
(In reply to comment #2) > Created attachment 275923 [details] > build log for rdb set What would be really helpful in this case would be the config.log
Doug: at your service; eeeh, testuser@archtester ~ $ ls /mnt/gen2/tmpdir/portage/app-emulation/qemu-kvm-0.14.1-r1/temp build.log eclass-debug.log environment logging testuser@archtester ~ $ ls /mnt/gen2/tmpdir/portage/app-emulation/qemu-kvm-0.14.1-r1/temp/logging/ testuser@archtester ~ $ Let's go for, how does one get the ebuild to make one??!?? Or have I stumbled on yet another bug??!?
(In reply to comment #5) > Thank you. I've also made a few other tweaks to debug flags and now USE=debug > should build. yes, good work. With the latest ebuild, emerges with use debug
(In reply to comment #8) > Doug: at your service; eeeh, > > testuser@archtester ~ $ ls > /mnt/gen2/tmpdir/portage/app-emulation/qemu-kvm-0.14.1-r1/temp > build.log eclass-debug.log environment logging > testuser@archtester ~ $ ls > /mnt/gen2/tmpdir/portage/app-emulation/qemu-kvm-0.14.1-r1/temp/logging/ > testuser@archtester ~ $ > > > Let's go for, how does one get the ebuild to make one??!?? > Or have I stumbled on yet another bug??!? temp is just for Portage. I'm talking about config.log in the work directory in the source directory.
Created attachment 276389 [details] The config.log here the config.log, just where you said.
also xen use flag are affected, i.e * Building the following softmmu targets: i386-softmmu x86_64-softmmu * Building the following user targets: i386-linux-user x86_64-linux-user ERROR ERROR: User requested feature xen ERROR: configure was not able to find it ERROR * ERROR: app-emulation/qemu-kvm-0.14.1-r1 failed (configure phase): * configure failed * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 3479: Called die * The specific snippet of code: * ./configure --prefix=/usr --disable-strip --disable-werror --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"
My USE flag: [ebuild R ] app-emulation/qemu-kvm-0.14.1-r1 USE="aio ncurses sasl ssl threads vhost-net* xen* -alsa -bluetooth -brltty -curl -debug -esd -fdt -hardened -jpeg -png -pulseaudio -qemu-ifup -rbd -sdl -spice -vde (-static%)" QEMU_SOFTMMU_TARGETS="i386 x86_64 -arm -cris -m68k -microblaze -mips -mips64 -mips64el -mipsel -ppc -ppc64 -ppcemb -sh4 -sh4eb -sparc -sparc64" QEMU_USER_TARGETS="i386 x86_64 -alpha -arm -armeb -cris -m68k -microblaze -mips -mipsel -ppc -ppc64 -ppc64abi32 -sh4 -sh4eb -sparc -sparc32plus -sparc64" 0 kB
(In reply to comment #12) > also xen use flag are affected, i.e > * Building the following softmmu targets: i386-softmmu x86_64-softmmu > * Building the following user targets: i386-linux-user x86_64-linux-user > ERROR > ERROR: User requested feature xen > ERROR: configure was not able to find it > ERROR > * ERROR: app-emulation/qemu-kvm-0.14.1-r1 failed (configure phase): > * configure failed > * > * Call stack: > * ebuild.sh, line 56: Called src_configure > * environment, line 3479: Called die > * The specific snippet of code: > * ./configure --prefix=/usr --disable-strip --disable-werror > --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" Open a different ticket and attach your config.log
why is this not tied off resolved? gentoo64-vm idella # emerge qemu-kvm -pv [ebuild N ] app-emulation/qemu-kvm-0.13.0-r2 USE="aio alsa bluetooth \ jpeg ncurses png sdl ssl -brltty -curl -esd -fdt -hardened -pulseaudio \ -qemu-ifup -sasl -static -vde" apart from whether spice ought be in or out. xen arguably never had any place in the set of use flags since they counter one one aother. It is now removed.
I was interested in rbd support. Last I checked it didn't compile, now it does (at least for me), but requires one to unmask the rbd use flag. So, to me at least, the rbd use flag should be unmasked before this bug is marked resolved.
yes rbd would be ok. however, the xen flag which I didn't include in this is problematic. I think I didn't even enable it in initial testing because it was so out of place. I thought it had been masked, but it is still in place.
(In reply to comment #16) > I was interested in rbd support. Last I checked it didn't compile, now it does > (at least for me), but requires one to unmask the rbd use flag. > > So, to me at least, the rbd use flag should be unmasked before this bug is > marked resolved. Until sys-cluster/ceph is marked stable, you'll have to unmask the rbd use flag if you want to use it.
USE=static and USE=debug should be fixed by now in 1.0 and likely 0.15-r1. USE=rbd is an unknown since its still masked. So if someone wants to test, that would be appreciated.
