I was not cross posting. Posted on this thread after you mentioned in your post that writing on msysgit user group is futile. Thought I wouldn't get further replies on my questions there. Plus I got a feeling that I will get more in depth information here. Sorry if I sent a wrong message > On Apr 9, 2015, at 6:27 AM, Konstantin Khomoutov <flatworm@xxxxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, 08 Apr 2015 23:58:58 +0200 > Thomas Braun <thomas.braun@xxxxxxxxxxxxxxxxxxx> wrote: > > [...] >>> I am trying to run the latest git 1.9.5 installer on windows. When I >>> run strings on libneon-25.dll it shows this: >>> >>> ./libneon-25.dll: OpenSSL 1.0.1h 5 Jun 2014 >>> >>> But when I load this dll in dependency walker, it picks up >>> msys-openssl 1.0.1m and has no trace of openssl-1.0.1h. My questions >>> to you: >>> >>> 1. Is libneon-25.dll statically linked with openssl-1.0.1h? >>> 2. If not, where is the reference to 1.0.1h coming from? >> >> I would be suprised if we link openssl statically into libneon. I >> guess libneon just reports against which openssl version it was >> *built*. >> >>> I am asked to rebuild git with libneon-25.dll linked against >>> openssl-1.0.1m. But I am having a feeling that this is not needed, >>> since libneon is already picking the latest openssl version. Can you >>> please confirm? >> >> You can download the development enviroment for git for windows here >> [1]. After installation, checkout the msys branch and then you can try >> to recomplile libneon using /src/subversion/release.sh. >> >> [1]: >> https://github.com/msysgit/msysgit/releases/download/Git-1.9.5-preview20150319/msysGit-netinstall-1.9.5-preview20150319.exe > [...] > > JFTR, the discussion about the same issue has been brought up on > git-users as well [2]. > > (People should really somehow use the basics of netiquette and mention > in their posts where they cross-post things.) > > 2. https://groups.google.com/d/topic/git-users/WXyWE5_JfNc/discussion -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html