Hi, the above mentioned version seems to be missing a dependency... It needs net-misc/curl ( and dev-python/pycurl reemerged) emerged with USE="-gnutls" otherwise it will fail with an "undefined symbol: gcry_control". Reproducible: Always Steps to Reproduce: 1. emerge net-misc/curl with USE="-gnutls" 2. reemerge dev-python/pycurl 3. emerge urlgrabber, this will fail
build log first. But if my hunch is correct, it's simply one of the libs on your system is broken with net-libs/gnutls[nettle].
1) Please post your `emerge --info' output in a comment. 2) Please attach the entire build log to this bug report.
Created attachment 305985 [details] build.log
Given the build log, change of plans: urlgrabber is irrelevant, what's your version of dev-python/pycurl ? Also, what's the output of 'lddtree /usr/lib64/python2.7/site-packages/pycurl.so' ?
using "dev-python/pycurl-7.19.0" # ldd /usr/lib64/python2.7/site-packages/pycurl.so linux-vdso.so.1 => (0x00007fff817ff000) libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007fa81211a000) libpython2.7.so.1.0 => /usr/lib64/libpython2.7.so.1.0 (0x00007fa811d56000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa811b38000) libc.so.6 => /lib64/libc.so.6 (0x00007fa8117ac000) librt.so.1 => /lib64/librt.so.1 (0x00007fa8115a3000) libz.so.1 => /lib64/libz.so.1 (0x00007fa81138c000) libgnutls.so.26 => /usr/lib64/libgnutls.so.26 (0x00007fa8110d0000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fa810ecc000) libutil.so.1 => /lib64/libutil.so.1 (0x00007fa810cc8000) libm.so.6 => /lib64/libm.so.6 (0x00007fa810a45000) /lib64/ld-linux-x86-64.so.2 (0x00007fa812598000) libtasn1.so.3 => /usr/lib64/libtasn1.so.3 (0x00007fa810834000) libnettle.so.4 => /usr/lib64/libnettle.so.4 (0x00007fa81060b000) libgmp.so.10 => /usr/lib64/libgmp.so.10 (0x00007fa81039b000) libhogweed.so.2 => /usr/lib64/libhogweed.so.2 (0x00007fa810188000)
@comment 5: in such case, this is most likely a partial dupe of bug 329987.
This should be fixed in pycurl-7.19.0-r1, please comment on the older bug if it is not. *** This bug has been marked as a duplicate of bug 329987 ***