Presumably, MacPorts tries to avoid using tools from its own ports in general to avoid getting burned by the non-atomic upgrade process. But that may not be an issue for a tool that's only used in the fetch phase. If it did that, then the only missing piece would be a MacPorts does not use the curl 1 executable. It links to the system libcurl and calls into it directly.
FWIW, on Starting in Now that MacPorts has the ability to bundle libraries with base, and does so for tcl already, I am in favor of including our own up-to-date copy of libcurl, if that will help with anything. Since Apple no longer releases security updates for PPC machines, people probably shouldn't be running them anymore - and we shouldn't be encouraging it. The Power Mac G5 was discontinued August 7, Essentially - older Mac OS X releases should be treated like our 'other platform' support.
With outdated roots being a growing problem I don't see how a private copy of libcurl would help here.
2 – Compile from Source
Actually, based on what I see in macports. That seems somewhat inconsistent. I've verified that I can make the fetch work under So either Safari and Firefox are using curl-ca-bundle. Though if the only use of SSL in MacPorts tself is for fetching content that's independently checksum-verified, then it might be entirely reasonable for "fetch. But outdated roots isn't the issue, and if cert validation is considered unimportant see my last comment , then it wouldn't matter if it were.
It has always at least, since As noted above, though, starting in I added a link to a Apple Developer presentation. As an aside, I agree with static linking and the lack of a stable ABI. I was bitten by that yesterday. Is there somewhere to get a summary of this without signing up for an Apple account?
- Ludovic Rousseau's blog: Mac OS X Lion and OpenSSL.
- Subscribe to RSS.
- get sand in your crack at big mac.
- OpenSSL is deprecated in Lion.
- Coolest Guides On The Planet?
- Install and Configure wget on OS X 10.7+ and fix SSL GNUTLS error!
Short summary: OpenSSL developers are not interested in guaranteeing a binary-stable API, only source code compatibility, which means you need to recompile or you only get the old version possibly containing old, fixed security gaps. To be able to enforce binary stability and get our users security fixes even when we don't recompile our apps, they're creating CommonCrypto instead, which is binary stable. Nick Dowell Nick Dowell 1, 16 16 silver badges 17 17 bronze badges.
Tony Lee Tony Lee 4, 1 1 gold badge 24 24 silver badges 42 42 bronze badges. Featured on Meta. Congratulations to our 29 oldest beta sites - They're now no longer beta! Unicorn Meta Zoo 7: Interview with Nicolas.
- mpeg to mpg converter mac!
- lol patcher 0 kbps mac;
- minecraft forge download mac 1.3.2;
- # (GitHub fetches fail under OSX (and presumably )) – MacPorts?
- mac pro concealer and corrector palette!
- tema mac para windows 7 2013.
- Subscribe to RSS.
- OS X Mountain Lion Client And Server: A Review and History - Google Buku.
- video bei youtube download mac.
Experiment: closing and reopening happens at 3 votes for the next 30 days…. Do I still need to pass --with-openssl-dir to configure? So do I really have to install another openssl? Many thanks for your efforts here Carlo. But I think I have to go back to ruby 1.
Install openssl on Mac OSX
Take a look at ruby-build. Big song and dance. It is OpenSSL 1. And the suggested solution does not work, as the ruby configure does not understand the --with-openssl-dir flag. Yep, I just installed Ruby 2. I have spent the last couple of days struggling to get Ruby 2.
I would also appreciate some clear syntax and steps to compile Ruby 2. This is turning out to be much harder than I thought and from what I see has been a known issue for some months.
Mac OS and openssl - Ruby - Ruby-Forum
Any help or link to a site would be appreciated. I have Googled till my eyes bled and unfortunately the best site I found was mostly in Japanese. I was hoping to be able to avoid that and just compile from source. So, taking a leap of faith and combining that with the Chruby wiki, the final command that appears to have worked for me is:. The trick is to completely ignore the error message spit back from. Please use another openssl. It will not be installed.
If so, your ruby source must be damaged. There should be a lot of other stuff in the file. Reading the suggestions and linked discussions the the others have provided, I gave the --with-openssl-dir flag another chance as it seems still to be used despite of the warning.
Mac OSX fatal error: ‘openssl/sha.h’ file not found
Now I tried different path variants to point to my new openssl install. It seems so succeed when using the dir above the openssl bin dir. Previously I only tried the path to the binary and the path to its containing dir:.