Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libcurl >= 8.2.1 to avoid curl: (55) Failed sending data to the peer #106

Open
theAkito opened this issue Aug 11, 2023 · 2 comments
Open

Comments

@theAkito
Copy link

theAkito commented Aug 11, 2023

I experienced the issue described in curl/curl#10591.

Now, this library is based on this curl library (wrapper) for Nim.

I tried to manually "override" the libcurl used 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 libcurl edition.

@guzba
Copy link
Collaborator

guzba commented Aug 11, 2023

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
Copy link
Author

@guzba

Thank you for the questions. I think it wasn't easy for me to explain what I would have liked to suggest. 😄

Basically, I just want to use the libcurl I manually compiled, when running my program, rather than it choosing the default, system installed, library.

This sounds like a Nim solvable issue, but I could not find a way to succeed in it.

So, I suggested, that could be fixed & this fix could then be added to Puppy's documentation or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants