-
-
Notifications
You must be signed in to change notification settings - Fork 0
Error: linking with cc
failed: exit code: 1
#1
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
Comments
What is your OS? |
Linux (Arch) I ran it inside and outside of docker. Same problem. |
Let me take a look. The other day I remember having the same issue but I don't know what I did to solve it! 🤦♂️ |
I cannot reproduce it... Have you tried doing |
yes I faced this by running |
Which os/distro do you have? |
I tried to reproduce it both in a Mac and a pc with Ubuntu 18.04 |
I installed a new fresh Ubuntu 18.04, upgrade it, install the latest Rust nightly and still face exactly the same problem with the code that I've changed in the gist file Which version of OpenSSL do you have locally? Can you send me your Cargo.lock also? |
I get an openSSL error if I try your exact example. I'm trying to see what can be done. Does it work with the example I provided? Because I understood that this wasn't working for you, which doesn't seem to be the case. |
Your code works fine. Actually my code doesn't work with your instruction. |
Ok, now I got the same error as you. I got it wrong and thought you were having issues with the original code. I guess it would be helpful to open an issue in the azure-functions-rs repo, too. |
This issue from the reqwest repo seems to be related. |
In the meantime you can use |
My simple code, without "azure-functions-rs", works fine. The combination has a problem! |
So I'll close this issue. |
Thanks for the library :D
I used your way and faced an error.
You can see the changed code and also the error in the following link:
https://gist.github.com/omid/b55fe742e8bacff0c34042218de5d363
Any idea about the error?
There are several topics related to this, but I couldn't fix it, like:
rust-lang/rust#25289
The text was updated successfully, but these errors were encountered: