This is really frustrating. I keep getting this error when trying to run a standard curl command:
curl --url https://install.meteor.com | sh
curl: (48) An unknown option was passed in to libcurl
Anyone know how to fix it?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve just run into this problem myself. A bit of cursory research led me to this bug tracker entry, but updating didn’t do the trick. I recently built the newest version of
libcurlfrom source, though, so I figured it must be something to do with the directory structure getting mixed up. I’m sure you’re probably not in the exact same situation, but perhaps Mountain Lion introduced a similar enough error that the steps I took to fix the problem might be able to help.First, run
which curlto determine where the binary is being called from. Then make sure that location actually exists by runninglocate -r /curl$. If it doesn’t (this was the issue in my case), try runningcurlusing all of the full paths provided bylocate, ignoring the obviously superfluous ones likepython-pycurl.Once you’ve found one that works, you can either create a symlink to it from the one
whichfound, or else check to see whether removing the latter will allow the shell to find the correct one on its own. For me, the fix was as simple as removing/usr/local/bin/curl, causingwhich curlto correctly respond with/usr/bin/curlandcurlitself to return to normal operation.