Hi, Bug #605558 [1] is what caused libcurl to be compiled without c-ares support.
Is the problem still there? I tried to compile libcurl 7.22.0-3 with c-ares 1.7.5-1 and I could not reproduce the issue: $ curl -v http://security.debian.org * About to connect() to security.debian.org port 80 (#0) * Trying 2607:ea00:101:3c0b:207:e9ff:fe00:e595... Failed to connect to 2607:ea00:101:3c0b:207:e9ff:fe00:e595: Network is unreachable * Success * Trying 2001:4f8:8:36::6... Failed to connect to 2001:4f8:8:36::6: Network is unreachable * Success * Trying 128.31.0.36... connected [...] This makes me think the problem has been solved wither in curl or c-ares. It would be useful to have libcurl compiled with c-ares, because of [2]. Thank you, Ludovico [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605558 [2] http://stackoverflow.com/questions/9191668/error-longjmp-causes-uninitialized-stack-frame -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
