threads / discuss / 48229

Is support for 10.8 dropped?

Subject: Is support for 10.8 dropped?

## tl;dr

22 messages between Apr 5, 2018 and May 7, 2018.

replies: 21people: 5as markdown or json

Igor Korot· Apr 5, 2018, 19:48 UTC · lore

Hi, ALL, I am a successful user of git and my project is locad on GitHub (still in development).

I have console git client installed on all 3 major platforms - Windows, Linux and Mac.

Up until recently everything was working fine. However about a month ago I started experiencing issues with OSX.

I am running OSX 10.8 and initially I was receiving the following:

[quote] fatal: unable to access 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version [/quote].

After asking on the stackoverflow I received a suggestion of updating the git application. I did that successfully) and now am getting the following:

[quote]
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
[/quote]

Now my question is - how I can upgrade the git console client for my OSX version? It looks like all installers are written for 10.9+ and the only way to work it is to update the OS?

Is there a version of the git console app for OSX 10.8?
Thank you.
Eric Sunshine· Apr 5, 2018, 21:46 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Thu, Apr 5, 2018 at 3:48 PM, Igor Korot <ikorot01@gmail.com> wrote:
> Is support for 10.8 dropped?

Until about a year ago, I was still periodically building Git from source on MacOS 10.5, and there hasn't been any outright effort to drop support for older MacOS, so I expect that 10.8 is still supported by the Git project itself.

However, whether various packagers of (pre-built) Git support 10.8 is a different matter.

Show 13 quoted lines
> 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
>
> Now my question is - how I can upgrade the git console client for my
> OSX version?
> It looks like all installers are written for 10.9+ and the only way to
> work it is to update the OS?
>
> Is there a version of the git console app for OSX 10.8?

It's not clear what installer you used? Was it the package from git-scm? Was it from Homebrew?

I would guess that, even if the git-scm installer no longer supports 10.8, it is likely that Homebrew does. Have you tried it?

If both those options fail, you can always build from source.
Igor Korot· Apr 7, 2018, 02:20 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Hi, Eric,
On Thu, Apr 5, 2018 at 5:46 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 7 quoted lines
> On Thu, Apr 5, 2018 at 3:48 PM, Igor Korot <ikorot01@gmail.com> wrote:
>> Is support for 10.8 dropped?
>
> Until about a year ago, I was still periodically building Git from
> source on MacOS 10.5, and there hasn't been any outright effort to
> drop support for older MacOS, so I expect that 10.8 is still supported
> by the Git project itself.
This is promising...
Show 20 quoted lines
>
> However, whether various packagers of (pre-built) Git support 10.8 is
> a different matter.
>
>> 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
>>
>> Now my question is - how I can upgrade the git console client for my
>> OSX version?
>> It looks like all installers are written for 10.9+ and the only way to
>> work it is to update the OS?
>>
>> Is there a version of the git console app for OSX 10.8?
>
> It's not clear what installer you used? Was it the package from
> git-scm? Was it from Homebrew?

I just tried the git-scm installer and got exactly the same error during the runtime.

>
> I would guess that, even if the git-scm installer no longer supports
> 10.8, it is likely that Homebrew does. Have you tried it?
I don't want to pollute my system with Homebrew.
>
> If both those options fail, you can always build from source.

Where do I get the soure code? And how do I build it? I guess I have only one option left. ;-)

Thank you.
Eric Sunshine· Apr 7, 2018, 07:32 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Fri, Apr 6, 2018 at 10:20 PM, Igor Korot <ikorot01@gmail.com> wrote:
Show 9 quoted lines
>>> 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
>>
>> It's not clear what installer you used? Was it the package from
>> git-scm? Was it from Homebrew?
>
> I just tried the git-scm installer and got exactly the same error
> during the runtime.
Have you tried any of the suggestions at these pages for resolving this issue?
https://stackoverflow.com/questions/22920497/git-mountain-lion-dyld-lazy-symbol-binding-failed-symbol-not-found-str
https://stackoverflow.com/questions/20929689/git-commands-not-working-in-mac-terminal-dyld-symbol-not-found-strlcpy-ch
Show 9 quoted lines
>> I would guess that, even if the git-scm installer no longer supports
>> 10.8, it is likely that Homebrew does. Have you tried it?
>
> I don't want to pollute my system with Homebrew.
>
>> If both those options fail, you can always build from source.
>
> Where do I get the soure code? And how do I build it?
> I guess I have only one option left. ;-)

Source code for the latest release is at: https://github.com/git/git/archive/v2.17.0.zip

To build it, you'll need to have the MacOS Developer Tools installed. It's also quite likely that you'll need to build some prerequisite libraries; at minimum OpenSSL. You may be able to skip other libraries if you don't care about the functionality. Build settings which you may need to adjust to disable dependence on libraries in which you're not interested are documented at the top of Makefile. Place overrides for those settings in a file named config.mak in the git directory.

Igor Korot· Apr 8, 2018, 21:10 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Hi, Eric, First of, I already have Xcode installed along with the Developer Tools. Second, here is the list of the different dylib files I found on my system:

MyMac:/ igorkorot$ find . -name libSystem.B.dylib ./Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk/usr/lib/libSystem.B.dylib ./Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib/libSystem.B.dylib ./Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib/libSystem.B.dylib ./usr/lib/libSystem.B.dylib

I'm hoping that the dylib in the MacOSX10.9 directory does have that symbol and maybe if I can check I can export this directory and let the linker pick it up.

And apparently I was wrong:
MyMac:/ igorkorot$ nm -gU
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib/libSystem.B.dylib
| grep strlcpy
MyMac:/ igorkorot$ nm -gU
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib/libSystem.B.dylib
| grep strlcpy
MyMac:/ igorkorot$
I can try to build from source as this becomes my last resort. ;-)
Thank you.
On Sat, Apr 7, 2018 at 3:32 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 37 quoted lines
> On Fri, Apr 6, 2018 at 10:20 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>>> 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
>>>
>>> It's not clear what installer you used? Was it the package from
>>> git-scm? Was it from Homebrew?
>>
>> I just tried the git-scm installer and got exactly the same error
>> during the runtime.
>
> Have you tried any of the suggestions at these pages for resolving this issue?
>
> https://stackoverflow.com/questions/22920497/git-mountain-lion-dyld-lazy-symbol-binding-failed-symbol-not-found-str
>
> https://stackoverflow.com/questions/20929689/git-commands-not-working-in-mac-terminal-dyld-symbol-not-found-strlcpy-ch
>
>>> I would guess that, even if the git-scm installer no longer supports
>>> 10.8, it is likely that Homebrew does. Have you tried it?
>>
>> I don't want to pollute my system with Homebrew.
>>
>>> If both those options fail, you can always build from source.
>>
>> Where do I get the soure code? And how do I build it?
>> I guess I have only one option left. ;-)
>
> Source code for the latest release is at:
> https://github.com/git/git/archive/v2.17.0.zip
>
> To build it, you'll need to have the MacOS Developer Tools installed.
> It's also quite likely that you'll need to build some prerequisite
> libraries; at minimum OpenSSL. You may be able to skip other libraries
> if you don't care about the functionality. Build settings which you
> may need to adjust to disable dependence on libraries in which you're
> not interested are documented at the top of Makefile. Place overrides
> for those settings in a file named config.mak in the git directory.
Igor Korot· Apr 8, 2018, 22:37 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

Eric, Sorry for multiple e-mails. I'm just trying to go thru with this.

This is what I tried:
[code]
MyMac:git-2.17.0 igorkorot$ make configure
GIT_VERSION = 2.17.0
    GEN configure
/bin/sh: autoconf: command not found
make: *** [configure] Error 127
MyMac:git-2.17.0 igorkorot$
[/code]
Does this mean that something is a miss?
Thank you.
On Sun, Apr 8, 2018 at 5:10 PM, Igor Korot <ikorot01@gmail.com> wrote:
Show 67 quoted lines
> Hi, Eric,
> First of, I already have Xcode installed along with the Developer Tools.
> Second, here is the list of the different dylib files I found on my system:
>
> MyMac:/ igorkorot$ find . -name libSystem.B.dylib
> ./Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk/usr/lib/libSystem.B.dylib
> ./Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib/libSystem.B.dylib
> ./Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib/libSystem.B.dylib
> ./usr/lib/libSystem.B.dylib
>
> I'm hoping that the dylib in the MacOSX10.9 directory does have that
> symbol and maybe if I can check I can export this directory and let
> the linker pick it up.
>
> And apparently I was wrong:
>
> MyMac:/ igorkorot$ nm -gU
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib/libSystem.B.dylib
> | grep strlcpy
> MyMac:/ igorkorot$ nm -gU
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib/libSystem.B.dylib
> | grep strlcpy
> MyMac:/ igorkorot$
>
> I can try to build from source as this becomes my last resort. ;-)
>
> Thank you.
>
>
> On Sat, Apr 7, 2018 at 3:32 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
>> On Fri, Apr 6, 2018 at 10:20 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>>>> 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
>>>>
>>>> It's not clear what installer you used? Was it the package from
>>>> git-scm? Was it from Homebrew?
>>>
>>> I just tried the git-scm installer and got exactly the same error
>>> during the runtime.
>>
>> Have you tried any of the suggestions at these pages for resolving this issue?
>>
>> https://stackoverflow.com/questions/22920497/git-mountain-lion-dyld-lazy-symbol-binding-failed-symbol-not-found-str
>>
>> https://stackoverflow.com/questions/20929689/git-commands-not-working-in-mac-terminal-dyld-symbol-not-found-strlcpy-ch
>>
>>>> I would guess that, even if the git-scm installer no longer supports
>>>> 10.8, it is likely that Homebrew does. Have you tried it?
>>>
>>> I don't want to pollute my system with Homebrew.
>>>
>>>> If both those options fail, you can always build from source.
>>>
>>> Where do I get the soure code? And how do I build it?
>>> I guess I have only one option left. ;-)
>>
>> Source code for the latest release is at:
>> https://github.com/git/git/archive/v2.17.0.zip
>>
>> To build it, you'll need to have the MacOS Developer Tools installed.
>> It's also quite likely that you'll need to build some prerequisite
>> libraries; at minimum OpenSSL. You may be able to skip other libraries
>> if you don't care about the functionality. Build settings which you
>> may need to adjust to disable dependence on libraries in which you're
>> not interested are documented at the top of Makefile. Place overrides
>> for those settings in a file named config.mak in the git directory.
Eric Sunshine· Apr 8, 2018, 23:23 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Sun, Apr 8, 2018 at 6:37 PM, Igor Korot <ikorot01@gmail.com> wrote:
Show 7 quoted lines
> MyMac:git-2.17.0 igorkorot$ make configure
> GIT_VERSION = 2.17.0
>     GEN configure
> /bin/sh: autoconf: command not found
> make: *** [configure] Error 127
>
> Does this mean that something is a miss?

That means that you don't have the Autoconf tools installed, but don't worry about it since use of the 'configure' script it very optional in this project. Git tends to build just fine on most platforms without running 'configure'. You should be able to get by just by typing "make" in the git directory after downloading the source.

And, as noted earlier, before running "make", you may need to create config.mak to override some settings documented at the top of Makefile (in particular, you may want to set NO_GETTEXT if you don't want to install gettext and don't think you'll need it). As prerequisite, you'll probably need to install OpenSSL.

Eric Sunshine· Apr 8, 2018, 23:59 UTC · lore

Re: Is support for 10.8 dropped?

On Sun, Apr 8, 2018 at 7:55 PM, Igor Korot <ikorot01@gmail.com> wrote:
Show 8 quoted lines
> On Sun, Apr 8, 2018, 6:23 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
>> And, as noted earlier, before running "make", you may need to create
>> config.mak to override some settings documented at the top of Makefile
>> (in particular, you may want to set NO_GETTEXT if you don't want to
>> install gettext and don't think you'll need it). As prerequisite,
>> you'll probably need to install OpenSSL.
>
> Is there a way to check for OpenSSL presence?

Not sure what you're asking. Are you asking how to determine if you already have OpenSSL built on your machine?

Note that you might be able to get by without installing OpenSSL since Git will try to use Apple's "Common Crypto" instead, so you could define NO_OPENSSL in config.mak and see if the project builds.

Igor Korot· Apr 11, 2018, 04:28 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Hi, Eric,
Sorry for the long delay.
On Sun, Apr 8, 2018 at 7:59 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 12 quoted lines
> On Sun, Apr 8, 2018 at 7:55 PM, Igor Korot <ikorot01@gmail.com> wrote:
>> On Sun, Apr 8, 2018, 6:23 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
>>> And, as noted earlier, before running "make", you may need to create
>>> config.mak to override some settings documented at the top of Makefile
>>> (in particular, you may want to set NO_GETTEXT if you don't want to
>>> install gettext and don't think you'll need it). As prerequisite,
>>> you'll probably need to install OpenSSL.
>>
>> Is there a way to check for OpenSSL presence?
>
> Not sure what you're asking. Are you asking how to determine if you
> already have OpenSSL built on your machine?
Yes, that's what I was asking...
>
> Note that you might be able to get by without installing OpenSSL since
> Git will try to use Apple's "Common Crypto" instead, so you could
> define NO_OPENSSL in config.mak and see if the project builds.
This is what I got trying to do just "make":
MyMac:git-2.17.0 igorkorot$ make
    * new build flags
    CC credential-store.o
In file included from credential-store.c:1:
In file included from ./cache.h:9:
./gettext.h:17:11: fatal error: 'libintl.h' file not found
#       include <libintl.h>
                ^
1 error generated.
make: *** [credential-store.o] Error 1
And I am also confused. Which file am I suppose to modify here?

MyMac:git-2.17.0 igorkorot$ ls -la conf* -rwxr-xr-x@ 1 igorkorot staff 74461 Apr 2 10:13 config.c -rwxr-xr-x@ 1 igorkorot staff 9888 Apr 2 10:13 config.h -rwxr-xr-x@ 1 igorkorot staff 540 Apr 2 10:13 config.mak.in -rwxr-xr-x@ 1 igorkorot staff 16940 Apr 2 10:13 config.mak.uname -rwxr-xr-x@ 1 igorkorot staff 37509 Apr 2 10:13 configure.ac -rw-r--r-- 1 igorkorot staff 37500 Apr 8 18:52 configure.ac+

Thank you.
Eric Sunshine· Apr 11, 2018, 09:44 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Wed, Apr 11, 2018 at 12:28 AM, Igor Korot <ikorot01@gmail.com> wrote:
Show 6 quoted lines
>>> Is there a way to check for OpenSSL presence?
>>
>> Not sure what you're asking. Are you asking how to determine if you
>> already have OpenSSL built on your machine?
>
> Yes, that's what I was asking...
Easiest way to determine it is to try to compile Git without setting NO_OPENSSL.
Show 11 quoted lines
> This is what I got trying to do just "make":
>
> MyMac:git-2.17.0 igorkorot$ make
>     * new build flags
>     CC credential-store.o
> In file included from credential-store.c:1:
> In file included from ./cache.h:9:
> ./gettext.h:17:11: fatal error: 'libintl.h' file not found
> #       include <libintl.h>
>                 ^
> 1 error generated.

This is because you don't have gettext installed. You should be able to set NO_GETTEXT to work around this.

Show 9 quoted lines
> And I am also confused. Which file am I suppose to modify here?
>
> MyMac:git-2.17.0 igorkorot$ ls -la conf*
> -rwxr-xr-x@ 1 igorkorot  staff  74461 Apr  2 10:13 config.c
> -rwxr-xr-x@ 1 igorkorot  staff   9888 Apr  2 10:13 config.h
> -rwxr-xr-x@ 1 igorkorot  staff    540 Apr  2 10:13 config.mak.in
> -rwxr-xr-x@ 1 igorkorot  staff  16940 Apr  2 10:13 config.mak.uname
> -rwxr-xr-x@ 1 igorkorot  staff  37509 Apr  2 10:13 configure.ac
> -rw-r--r--  1 igorkorot  staff  37500 Apr  8 18:52 configure.ac+

You should create a new file named "config.mak". For instance, the content of your config.mak file might be:

    NO_GETTEXT=Yes
Igor Korot· Apr 22, 2018, 05:15 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Hi, Sorry for the long delay. Been busy with life things.

I built git from sources. The build was successful.

[code] MyMac:git-2.17.0 igorkorot$ cat config.mak NO_GETTEXT=Yes NO_OPENSSL=Yes [/code]

Next I tried to do git pull for my project:

[code] MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull fatal: unable to access 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version MyMac:dbhandler igorkorot$ [/code]

Thank you.
On Wed, Apr 11, 2018 at 5:44 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 39 quoted lines
> On Wed, Apr 11, 2018 at 12:28 AM, Igor Korot <ikorot01@gmail.com> wrote:
>>>> Is there a way to check for OpenSSL presence?
>>>
>>> Not sure what you're asking. Are you asking how to determine if you
>>> already have OpenSSL built on your machine?
>>
>> Yes, that's what I was asking...
>
> Easiest way to determine it is to try to compile Git without setting NO_OPENSSL.
>
>> This is what I got trying to do just "make":
>>
>> MyMac:git-2.17.0 igorkorot$ make
>>     * new build flags
>>     CC credential-store.o
>> In file included from credential-store.c:1:
>> In file included from ./cache.h:9:
>> ./gettext.h:17:11: fatal error: 'libintl.h' file not found
>> #       include <libintl.h>
>>                 ^
>> 1 error generated.
>
> This is because you don't have gettext installed. You should be able
> to set NO_GETTEXT to work around this.
>
>> And I am also confused. Which file am I suppose to modify here?
>>
>> MyMac:git-2.17.0 igorkorot$ ls -la conf*
>> -rwxr-xr-x@ 1 igorkorot  staff  74461 Apr  2 10:13 config.c
>> -rwxr-xr-x@ 1 igorkorot  staff   9888 Apr  2 10:13 config.h
>> -rwxr-xr-x@ 1 igorkorot  staff    540 Apr  2 10:13 config.mak.in
>> -rwxr-xr-x@ 1 igorkorot  staff  16940 Apr  2 10:13 config.mak.uname
>> -rwxr-xr-x@ 1 igorkorot  staff  37509 Apr  2 10:13 configure.ac
>> -rw-r--r--  1 igorkorot  staff  37500 Apr  8 18:52 configure.ac+
>
> You should create a new file named "config.mak". For instance, the
> content of your config.mak file might be:
>
>     NO_GETTEXT=Yes
Eric Sunshine· Apr 22, 2018, 05:37 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
Show 9 quoted lines
> MyMac:git-2.17.0 igorkorot$ cat config.mak
> NO_GETTEXT=Yes
> NO_OPENSSL=Yes
>
> MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
> fatal: unable to access
> 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
> routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
> MyMac:dbhandler igorkorot$

Try re-building with OpenSSL enabled (remove NO_OPENSSL from config.make). You may need to build/install OpenSSL yourself to get this to work.

Perry Hutchison· Apr 22, 2018, 07:10 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Eric Sunshine <sunshine@sunshineco.us> wrote:
Show 14 quoted lines
> On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
> > MyMac:git-2.17.0 igorkorot$ cat config.mak
> > NO_GETTEXT=Yes
> > NO_OPENSSL=Yes
> >
> > MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
> > fatal: unable to access
> > 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
> > routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
> > MyMac:dbhandler igorkorot$
>
> Try re-building with OpenSSL enabled (remove NO_OPENSSL from
> config.make). You may need to build/install OpenSSL yourself to get
> this to work.
Explanation:  "tlsv1 alert protocol version" means that the server
requires its clients to use a newer version of TLS than what was
used in the local build of git.
brian m. carlson· Apr 22, 2018, 17:49 UTC · re: Perry Hutchison · lore

Re: Is support for 10.8 dropped?

On Sun, Apr 22, 2018 at 12:10:20AM -0700, Perry Hutchison wrote:
Show 19 quoted lines
> Eric Sunshine <sunshine@sunshineco.us> wrote:
> > On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
> > > MyMac:git-2.17.0 igorkorot$ cat config.mak
> > > NO_GETTEXT=Yes
> > > NO_OPENSSL=Yes
> > >
> > > MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
> > > fatal: unable to access
> > > 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
> > > routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
> > > MyMac:dbhandler igorkorot$
> >
> > Try re-building with OpenSSL enabled (remove NO_OPENSSL from
> > config.make). You may need to build/install OpenSSL yourself to get
> > this to work.
> 
> Explanation:  "tlsv1 alert protocol version" means that the server
> requires its clients to use a newer version of TLS than what was
> used in the local build of git.

I think the issue here is that you're using a crypto library which may only support TLS 1.0 on 10.8[0]. GitHub requires TLS 1.2 as of recently. So this isn't really a problem with Git, so much as it's an incompatibility between the version of the crypto library you're using and GitHub.

I expect that due to the PCI DSS rules prohibiting new deployment of TLS 1.0, you'll continue to run into this issue more and more unless you upgrade to an OS or crypto library that supports TLS 1.2. As of June 30, TLS 1.0 will be pretty much dead on the Internet.

[0] I surmised this from https://www.ssllabs.com/ssltest/clients.html, but I don't use macOS so can't speak for certain.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Igor Korot· Apr 23, 2018, 16:39 UTC · re: brian m. carlson · lore

Re: Is support for 10.8 dropped?

Hi, Brian,

On Sun, Apr 22, 2018 at 12:49 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 31 quoted lines
> On Sun, Apr 22, 2018 at 12:10:20AM -0700, Perry Hutchison wrote:
>> Eric Sunshine <sunshine@sunshineco.us> wrote:
>> > On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
>> > > MyMac:git-2.17.0 igorkorot$ cat config.mak
>> > > NO_GETTEXT=Yes
>> > > NO_OPENSSL=Yes
>> > >
>> > > MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
>> > > fatal: unable to access
>> > > 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
>> > > routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
>> > > MyMac:dbhandler igorkorot$
>> >
>> > Try re-building with OpenSSL enabled (remove NO_OPENSSL from
>> > config.make). You may need to build/install OpenSSL yourself to get
>> > this to work.
>>
>> Explanation:  "tlsv1 alert protocol version" means that the server
>> requires its clients to use a newer version of TLS than what was
>> used in the local build of git.
>
> I think the issue here is that you're using a crypto library which may
> only support TLS 1.0 on 10.8[0].  GitHub requires TLS 1.2 as of
> recently.  So this isn't really a problem with Git, so much as it's an
> incompatibility between the version of the crypto library you're using
> and GitHub.
>
> I expect that due to the PCI DSS rules prohibiting new deployment of TLS
> 1.0, you'll continue to run into this issue more and more unless you
> upgrade to an OS or crypto library that supports TLS 1.2.  As of June
> 30, TLS 1.0 will be pretty much dead on the Internet.

Yes, openSSL on OSX 10.8 is old. I will t to update it tonight. But as a developer I'm trying to stay with whatever OS provides. Because upgrading will actually means that I will have to recompile an re-test everything I made, since I will be working on a brand new system.

This is however is an unfortunate event when I will have to upgrade...
Than you.
Show 6 quoted lines
>
> [0] I surmised this from https://www.ssllabs.com/ssltest/clients.html,
> but I don't use macOS so can't speak for certain.
> --
> brian m. carlson: Houston, Texas, US
> OpenPGP: https://keybase.io/bk2204
Igor Korot· Apr 23, 2018, 16:31 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Hi, Eric,
On Sun, Apr 22, 2018 at 12:37 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 14 quoted lines
> On Sun, Apr 22, 2018 at 1:15 AM, Igor Korot <ikorot01@gmail.com> wrote:
>> MyMac:git-2.17.0 igorkorot$ cat config.mak
>> NO_GETTEXT=Yes
>> NO_OPENSSL=Yes
>>
>> MyMac:dbhandler igorkorot$ /Users/igorkorot/git-2.17.0/git pull
>> fatal: unable to access
>> 'https://github.com/oneeyeman1/dbhandler.git/': error:1407742E:SSL
>> routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
>> MyMac:dbhandler igorkorot$
>
> Try re-building with OpenSSL enabled (remove NO_OPENSSL from
> config.make). You may need to build/install OpenSSL yourself to get
> this to work.
2 things:
1. Is the file name "config.mak" or "config.make"?
2. Do I have to do "make clean" or just remove the line and o "make"?
Thank you.
Eric Sunshine· Apr 23, 2018, 16:53 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

On Mon, Apr 23, 2018 at 12:31 PM, Igor Korot <ikorot01@gmail.com> wrote:
> 1. Is the file name "config.mak" or "config.make"?
"config.mak"
> 2. Do I have to do "make clean" or just remove the line and o "make"?
"make clean" would not hurt.
Totsten Bögershausen· Apr 23, 2018, 19:58 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

On 2018-04-23 18:53, Eric Sunshine wrote:
> On Mon, Apr 23, 2018 at 12:31 PM, Igor Korot <ikorot01@gmail.com> wrote:
>> 1. Is the file name "config.mak" or "config.make"?
> 
> "config.mak"

I am confused, I have these file in my tree: config.mak.in config.mak.uname Makefile Setting options is documentend in Makefile

> 
>> 2. Do I have to do "make clean" or just remove the line and o "make"?
> 
> "make clean" would not hurt.

I would actually try to install openssl / openssl-dev (or however it is called) via "mac ports" or "home brew".

Both should work (but I don't have a system to test on)
Eric Sunshine· Apr 23, 2018, 21:04 UTC · re: Totsten Bögershausen · lore

Re: Is support for 10.8 dropped?

On Mon, Apr 23, 2018 at 3:58 PM, Totsten Bögershausen <tboegi@web.de> wrote:
Show 9 quoted lines
> On 2018-04-23 18:53, Eric Sunshine wrote:
>> On Mon, Apr 23, 2018 at 12:31 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>> 1. Is the file name "config.mak" or "config.make"?
>>
>> "config.mak"
>
> I am confused, I have these file in my tree:
> config.mak.in  config.mak.uname   Makefile
> Setting options is documentend in Makefile

You can place custom build settings in a file named "config.mak" which you create; it's not part of the distribution. The other files are not intended for modification.

> I would actually try to install openssl / openssl-dev (or however it is
> called) via "mac ports" or "home brew".
>
> Both should work (but I don't have a system to test on)
Igor indicated earlier[1] in the thread that he wanted to avoid
Homebrew (and Macports, etc., presumably). If he'd be willing to use
Homebrew, then easiest would be simply to install Git itself via
Homebrew: "brew install git"
[1]: https://public-inbox.org/git/CA+FnnTzfJMBuSMAD7PgUurRu8jOpirEgM6=+=i91zdGLWmfUpg@mail.gmail.com/
Igor Korot· Apr 23, 2018, 21:21 UTC · re: Eric Sunshine · lore

Re: Is support for 10.8 dropped?

Eric,
On Mon, Apr 23, 2018 at 4:04 PM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 24 quoted lines
> On Mon, Apr 23, 2018 at 3:58 PM, Totsten Bögershausen <tboegi@web.de> wrote:
>> On 2018-04-23 18:53, Eric Sunshine wrote:
>>> On Mon, Apr 23, 2018 at 12:31 PM, Igor Korot <ikorot01@gmail.com> wrote:
>>>> 1. Is the file name "config.mak" or "config.make"?
>>>
>>> "config.mak"
>>
>> I am confused, I have these file in my tree:
>> config.mak.in  config.mak.uname   Makefile
>> Setting options is documentend in Makefile
>
> You can place custom build settings in a file named "config.mak" which
> you create; it's not part of the distribution. The other files are not
> intended for modification.
>
>> I would actually try to install openssl / openssl-dev (or however it is
>> called) via "mac ports" or "home brew".
>>
>> Both should work (but I don't have a system to test on)
>
> Igor indicated earlier[1] in the thread that he wanted to avoid
> Homebrew (and Macports, etc., presumably). If he'd be willing to use
> Homebrew, then easiest would be simply to install Git itself via
> Homebrew: "brew install git"

Yes. This laptop is old and doesn't have too big of a hard drive. And I'm trying to create a big program

Thank you.
>
> [1]: https://public-inbox.org/git/CA+FnnTzfJMBuSMAD7PgUurRu8jOpirEgM6=+=i91zdGLWmfUpg@mail.gmail.com/
Perry Hutchison· Apr 23, 2018, 23:16 UTC · re: Igor Korot · lore

Re: Is support for 10.8 dropped?

Igor Korot <ikorot01@gmail.com> wrote:
> This laptop is old and doesn't have too big of a hard drive.
> And I'm trying to create a big program

Building OpenSSL via homebrew or MacPorts would likely take less space than building all of git that way, but if even that is too much perhaps it is time to consider moving the development environment onto an external hard drive (via USB, eSATA, or even FireWire) -- the presumption being that the development environment may not need to be lugged around when using the laptop as a laptop.

Igor Korot· May 7, 2018, 15:20 UTC · re: Perry Hutchison · lore

Re: Is support for 10.8 dropped?

Hi guys, I am going to try and build the OpenSSL and Git locally. Search brought me here: https://wiki.openssl.org/index.php/Compilation_and_Installation#OS_X.

Which options do I absolutely have to have for configuring OpenSSL? Should I exclude "no--ssl2"? "no-ssl3"?

Thank you.
On Mon, Apr 23, 2018 at 6:16 PM, Perry Hutchison <perryh@pluto.rain.com> wrote:
Show 10 quoted lines
> Igor Korot <ikorot01@gmail.com> wrote:
>> This laptop is old and doesn't have too big of a hard drive.
>> And I'm trying to create a big program
>
> Building OpenSSL via homebrew or MacPorts would likely take less
> space than building all of git that way, but if even that is
> too much perhaps it is time to consider moving the development
> environment onto an external hard drive (via USB, eSATA, or even
> FireWire) -- the presumption being that the development environment
> may not need to be lugged around when using the laptop as a laptop.

← back to recent threads