Okay, this is hairy. Curl will be linked against if its avaiable, breaking dependency-tracking badly even if you have USE="-curl" on systems. in totem, curl is used for automatic dll downloading on x86 systems. Here's the interesting code from configure.in : _system_is_x86="no" AC_CHECK_HEADER( asm/vm86.h, _system_is_x86="yes" ) if `test "x$_system_is_x86" = "xyes" && test "x$CURL_CONFIG" != "xno"` ; then HAVE_X86=1 AC_DEFINE(HAVE_X86, 1, [defined on x86 machines]) else HAVE_X86=0 fi AM_CONDITIONAL(HAVE_X86, `test "x$_system_is_x86" = "xyes" && test "x$CURL_CONFIG" != "xno"`) (( Note that CURL_CONFIG is set if curl is avaiable on the system. No way to replace it, and to hack the configure.in in this case is a mess (curl check is hairy )) Now, this X86 check is only true if it can find curl, and what it does is actually quite nifty: if totem can't find a dll decoder for a movie, it will attempt to download it. But, what actually disturbs me is that curl isn't disable'able if found. ( we can't just hack config.in, as its not referred to there before linking :/ ) solutions DEPEND="x86? ( curl )" or deep-hack on configure.in ... Somehow i suspect that configure.in hacking would be the prettiest over all.
yep fix configure.in and send a patch upstream :) I knew about this one, only non-switchable optional deps are not really a priority to me at this time. Fixing it with a USE flag as suggested (would need to be x86 & curl btw) is flawed beyond the initial install.
configure.in fixed in 0.99.8-r1 moved the curl? () into the !gstreamer () block, because its never used without xine backend. some other comments on it please
hmm i actually noticed this patch & the automake breaking the configure step for me. Haven't really looked into why. Something about '--exists' not being valid.
--exists? Weird, since the patch doesn't touch anything such. the patch just wraps a --disable/--enable around the header check..
tried some rudimentary tests USE +/- curl and running the config tests, and couldn't find any exists output, do you have a log or a reproducible case?
Using autoconf-2.58 i can consistently reproduce it using the xine backend and USE=-curl (and i don't have curl installed). checking for curl... configure: WARNING: curl development libraries missing checking for glib-2.0 >= 2.1.0 libgnomeui-2.0 >= 2.1.1 libglade-2.0 gnome-vfs-2.0 >= 2.1.6 gnome-vfs-module-2.0 >= 2.1.6 gnome-desktop-2.0 >= 2.1.5 libxine >= 1.0.0 gconf-2.0... ./configure: line 8773: --exists: command not found ./configure: line 1: --errors-to-stdout: command not found It's in a line with '$PKG_CONFIG --exists', so i guess somehow the PKG_CONFIG var gets reset (?) Using the gstreamer backend goes fine, i guess becuase it skips the curl check all the way. I can attach full logs if you still can't reproduce it.
Nope, I can't reproduce it here with : USE="-curl xine -gstreamer" emerge totem, when I've removed the curl package completely.
i can still reproduce this, but since curl got ripped in later versions, closing this bug.
