From: Mamta <mamta.upadhyay@gmail.com>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Cc: Thomas Braun <thomas.braun@virtuell-zuhause.de>,
"git@vger.kernel.org" <git@vger.kernel.org>,
msysGit <msysgit@googlegroups.com>
Subject: Re: [msysGit] Re:
Date: Thu, 9 Apr 2015 09:35:28 -0500 [thread overview]
Message-ID: <88FC14EA-E627-40C7-BD22-A8DB687E55B6@gmail.com> (raw)
In-Reply-To: <20150409142716.bd75cc6b9e13dc580cdda722@domain007.com>
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@users.sourceforge.net> wrote:
>
> On Wed, 08 Apr 2015 23:58:58 +0200
> Thomas Braun <thomas.braun@virtuell-zuhause.de> 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
prev parent reply other threads:[~2015-04-09 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 20:44 (unknown), Mamta Upadhyay
2015-04-08 21:58 ` Thomas Braun
2015-04-09 11:27 ` Re: Konstantin Khomoutov
2015-04-09 14:35 ` Mamta [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88FC14EA-E627-40C7-BD22-A8DB687E55B6@gmail.com \
--to=mamta.upadhyay@gmail.com \
--cc=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=thomas.braun@virtuell-zuhause.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).