Created attachment 286031 [details] emerge --info =media-libs/libdv-1.0.0-r2 Trying to emerge -pqv =media-libs/libdv-1.0.0-r2 [ebuild R ] media-libs/libdv-1.0.0-r2 USE="-debug -sdl -static-libs% -xv" I got a ./configure error: [snip] checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether to enable debugging... default=yes checking for x86_64-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GTK... checking for XvQueryAdaptors in -lXv... no configure: error: Could not find Xv Lib As it merged correctly in the previous cycle (where USE="static-libs" was not defined) I presume this has been introduced by this new option.
Same problem here. A small mistake was apparently made when the static-libs use flag was added to the ebuild. The line with use_enable static-libs in the src_configure() function is missing a backslash at the end. Adding the backslash fixes the problem for me.
(In reply to comment #1) > Same problem here. > A small mistake was apparently made when the static-libs use flag was added to > the ebuild. > The line with use_enable static-libs in the src_configure() function is missing > a backslash at the end. Adding the backslash fixes the problem for me. Fixed here too! This backslash was tricky, thank you. I guess we could say resolved, but perhaps upstream must update the ebuild before that?
Please at least compile test if you edit stable ebuilds, committing to stable untested isn't that good idea
Suprisingly i test those, sadly it passed to build without issue on my pc so i didn't notice the trailing backslash. Installed versions: 1.0.0-r2(20:54:20 9.9.2011)(xv -debug -sdl -static-libs) Updated the ebuild.
