The procedure entry point curl_global_sslset could not be located in the dynamic link library libcurl-4.dll.

[brechtm]

• I was not able to find an open or closed issue matching what I'm seeing

Setup

• Which version of Git for Windows are you using? Is it 32-bit or 64-bit?

mingw-w64-x86_64-git-2.14.1.1.82d9b3f3b2-1 from the git-for-windows pacman repository.

$ git --version --build-options

git version 2.14.1.windows.1
built from commit: 82d9b3f3b2407b52251620597d4b14933685459d
sizeof-long: 4
machine: x86_64

• Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?

Windows 7 Enterprise SP1

$ cmd.exe /c ver

Microsoft Windows [Version 6.1.7601]

• What options did you set as part of the installation? Or did you choose the
  defaults?

I installed mingw-w64-x86_64-git in MSYS2.

• Any other interesting things about your environment that might be related
  to the issue you're seeing?

I'm running git-for-windows inside an MSYS2 installation as described here: https://stackoverflow.com/questions/40262434/what-are-the-differences-between-msys-git-and-git-for-windows-mingw-w64-x86-64-g

This was working well with previous versions of git-for-windows, up to and including mingw-w64-x86_64-git-2.13.2.1.914b84c9d9-1 (to which I've reverted for now). I am aware that this non-standard setup may be causing the crash.

Details

• Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

Bash and CMD

• What commands did you run to trigger this issue? If you can provide a
  Minimal, Complete, and Verifiable example
  this will help us understand the issue.

git fetch

• What did you expect to occur after running these commands?

A non-zero return code.

• What actually happened instead?

Bash: a return code of 128. No output or pop-up.
CMD: A pop-up dialog:

---------------------------
git-remote-ftp.exe - Entry Point Not Found
---------------------------
The procedure entry point curl_global_sslset could not be located in the dynamic link library libcurl-4.dll. 
---------------------------
OK   
---------------------------

[dscho]

Duplicate of #1268 (please really search existing tickets when asked to). You need to uninstall Gt completely and make sure C:\Program Files\Git was removed before reinstalling.

[brechtm]

I did inspect that issue. The error message is different. Plus I did not install Git using the installer but into MSYS2 using pacman.

[dscho]

If you install Git for Windows' Pacman package into MSYS2 without Git for Windows' other support packages, of course things break. That is to be expected. If you don't know the ramifications of what you did, it'd be better to stick with Git for Windows SDK instead.

[brechtm]

I understand this is not a supported way of installing git-for-windows. However, it was working without issues before. I'm trying to understand what changed since 2.13.2.1.914b84c9d9-1 to cause this.

[dscho]

@brechtm I am sympathetic to your reasoning. Please note, however, that I am not exactly in need for even more work, and you are putting more work on my shoulders.

The reason why you see this error is that I use an experimental cURL version in Git for Windows that has curl/curl#1601 integrated. This cURL version is not available in MSYS2, unless you install it specifically from Git for Windows' Pacman repository.

Of course, you can work around the reported issue by doing exactly as I said. The problem is that next time something similar happens, you will most likely have as little idea what happened as now because you are inactive in Git for Windows' development and therefore miss all the recent developments, so you will have to ask again, and I will have to set aside time again to address your problem, leaving other problems (that affect more than a single user) behind.

[brechtm]

Thanks @dscho. I appreciate you took the time to explain the cause of this crash. I can imagine you have enough work as it is, so I do not expect you to support this non-standard installation. So please do not feel obliged to spend time on this or similar tickets. I can live with an answer like "This is not a supported usage scenario for git-for-windows. I cannot afford to spend time investigating this issue". And this is basically all I can expect, seeing that you are doing this free of charge. Besides hoping for an answer to my question, I do think this ticket could be useful to others (however few) who run into the same problem.

Ideally, I would be using the git provided in the MSYS2 repository, but it suffers from some problems (detailed in the StackOverflow question I linked to above).

In any case, thanks for bringing a very useful piece of software to the Windows platform!

[brechtm]

Putting the git-for-windows and git-for-windows-mingw32 sections above the others as in the SDK's etc/pacman.conf seems to install the proper version of libcurl, making git work again.

[dscho]

@brechtm you are turning your MSYS2 installation into a Git for Windows SDK. The hard way. Probably you also want to install the git-extra package now, to fix up things in MSYS2 that are still incorrect.

[mishrsud]

Thanks @dscho, your tip to uninstall and reinstall git for windows worked perfectly. I was starting to lose my mind trying to figure out why I got the error message in the title of this thread after upgrading to "git version 2.14.1.windows.1"

[brechtm]

@dscho I can't remember why I opted for MSYS2 + the git-for-windows repository instead of the Git for Windows SDK. I suppose the SDK acts pretty much identical to MSYS2 with the exception of git, such as having the ability to upgrade packages using pacman? I'll replace MSYS2 with the SDK then if I run into any issues in the future.

[dscho]

@brechtm Git for Windows' SDK is nothing else than a special edition of MSYS2, indeed. As you found out, it adds (actually, prepends) two Pacman repositories, and it also installs the git-extra package which does a ton of modifications in its post install script to change things in MSYS2 that cannot be configured otherwise (such as patching a couple of overzealous commands in Bash's profile).

[Youda008]

This is not an issue of a single user. There is a good reason, why many of us would like to use git package in original msys2 instead of Git-For-Windows. Not all users want to have msys2 environment just for git and nothing else (which is what Git-For-Windows does), and it doesn't make sense to have 2 instances of msys2, first the original one with all the other packages and second one specialized only for git, packed together in Git-For-Windows. Then you can't the other Unix tools in Git-bash, because they are installed in the other msys2.