http://bugs.meego.com/show_bug.cgi?id=10015
--- Comment #14 from dwmw2 <[email protected]> 2010-11-24 03:53:13 PST --- I'm confused. libsoup-gnome should only be doing this crappy setenv thing if it's using a *really* old version of libproxy: AC_MSG_CHECKING(libproxy version) libproxy_version=`$PKG_CONFIG --modversion libproxy-1.0` case $libproxy_version in 0.2.*) AC_MSG_RESULT([$libproxy_version, using workarounds...]) AC_DEFINE(HAVE_LIBPROXY_WITH_NON_THREAD_SAFE_GNOME_MODULE, 1, [Defined if libproxy is old and has a non-thread-safe gnome module]) /* If we have a "bad" libproxy, set environment variables * and force it to use them. */ #ifdef HAVE_LIBPROXY_WITH_NON_THREAD_SAFE_GNOME_MODULE g_setenv ("PX_CONFIG_ORDER", "envvar", TRUE); if (http_proxy) g_setenv ("http_proxy", http_proxy, TRUE); We have never had libproxy 0.2 in MeeGo, although now we're using PacRunner it may advertise itself as 0.1. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
