guzba
commented
11 months ago Hello, I'd like to ask some clarifying questions because I am currently not sure what is being suggested or requested so that seems like a good first step.
I tried to manually "override" the libcurl used by Puppy/nim-libcurl, but it did not work out.
Do you mean that you tried to use your own version of nim-libcurl with changes to the C interface / bindings or something else? I'm not sure what you tried here or what problems you had and maybe that will be important to know.
Is there a way of publishing some general fix for everyone, to avoid this problem?
What general fix are you suggesting here and where specifically is the problem? Sorry, I just see that it appears a specific libcurl version had a problem that is fixed by an update. I'm not sure what we or the bindings would do to fix a bug in libcurl but perhaps with more info it'll become clear to me.
It'd be nice to have a generic go-to solution, when trying to run a program containing Puppy functionality with a custom libcurl edition.
I think Puppy doesn't care much about what libcurl version you use already, assuming it is interface compatible which seems to be the case. I think if I understood the issue better this would also make more sense to me.
Maybe I'm missing something obvious, in which case sorry for missing it! Hopefully though with some more info it'll help me understand things.
theAkito
I experienced the issue described in https://github.com/curl/curl/issues/10591.
Now, this library is based on this curl library (wrapper) for Nim.
I tried to manually "override" the
libcurlused by Puppy/nim-libcurl, but it did not work out.Is there a way of publishing some general fix for everyone, to avoid this problem?
It'd be nice to have a generic go-to solution, when trying to run a program containing Puppy functionality with a custom
libcurledition.