On Thu, Apr 04, 2013 at 23:14:02 -0000, Barry Warsaw wrote:
> I have a horribly ugly workaround for PyCurl in the works. I'll link a branch
> when ready, but I want to get Matthias's input to see if a toolchain fix is
> more appropriate.
(Since you have an environment set up to build the python-pycurl package
from source, it occurred to me to wonder:) How difficult would it be for
you to try building the package (without the workaround patch) against
libssl instead of libgnutls? That might be a fairly-easy way to test the
hypothesis that libgnutls is the underlying source of the problem...
On Thu, Apr 04, 2013 at 23:14:02 -0000, Barry Warsaw wrote:
> I have a horribly ugly workaround for PyCurl in the works. I'll link a branch
> when ready, but I want to get Matthias's input to see if a toolchain fix is
> more appropriate.
(Since you have an environment set up to build the python-pycurl package
from source, it occurred to me to wonder:) How difficult would it be for
you to try building the package (without the workaround patch) against
libssl instead of libgnutls? That might be a fairly-easy way to test the
hypothesis that libgnutls is the underlying source of the problem...
Nathan