git_osx_installer
git_osx_installer copied to clipboard
Problem upgrading on OSX 10.8.
Hi, I had to upgrade my git on OSX 10.8 because of the TLS switch. The installer ran successfully and the program was installed. I verified that by running:
[code] MyMac:dbhandler igorkorot$ /usr/local/git/bin/git --version git version 2.16.3 [/code]
However, trying to run it I received following:
[code] MyMac:dbhandler igorkorot$ /usr/local/git/bin/git pull dyld: lazy symbol binding failed: Symbol not found: ___strlcpy_chk Referenced from: /usr/local/git/libexec/git-core/git Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ___strlcpy_chk Referenced from: /usr/local/git/libexec/git-core/git Expected in: /usr/lib/libSystem.B.dylib
error: fetch died of signal 5 [/code]
Which means that this software is using the function which exist in the newer version of the OSX SDK.
Is it possible to make an update which will be compatible with OSX 10.8 during the run-time? I can help with the testing of this release.
TIA!!!
P.S.: I don't want to update my machine to High Sierra. The other library I use supports 10.7+ and it will be awhile since this suport will be dropped.
Until there's an update, the only version that supports GitHub requires Mavericks or later. I don't blame you for not wanting to use High Sierra; Sierra and High Sierra are a bit cancerous. El Capitan is probably the best place to be at the moment. I think you can download El Capitan from here: https://support.apple.com/en-us/HT206886
My computer only supports Lion, though, so I am dual-booting with Lubuntu to continue to use Git. It is not very pleasant.
OK, thank you. Do you think the update will happen soon? Maybe it is possible to compile this myself with the latest OpenSSL statically linked? Because there is no updates for OpenSSL through the OSX Preferences... Or maybe I can simply update OpenSSL myself?
Thank you.
I'm not expecting an update soon. It should somehow be possible to compile it yourself. I have no idea how, but it looks like the Snow Leopard builds of Git might be using the 32-bit branch of the project. It might be super complicated.
Maybe the easiest solution is to run Linux in a VMWare Fusion virtual machine.