From: Mike Hommey <mh@glandium.org>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: Why does git depend on two versions of libcrypto?
Date: Fri, 8 Feb 2008 11:03:47 +0100 [thread overview]
Message-ID: <20080208100346.GA20601@glandium.org> (raw)
In-Reply-To: <20080208104612.724d82ce@pc09.procura.nl>
On Fri, Feb 08, 2008 at 10:46:12AM +0100, H.Merijn Brand <h.m.brand@xs4all.nl> wrote:
> Don't know if this is a git question or a OpenSUSE question, but why does git
> depend on libcrypto.so.6 and not on libcrypto.so.0.9.8, like the rest does?
>
> Isn't that asking for trouble?
> In my case, they're both linked to the same lib, so I guess I'm safe.
(...)
> ldd[03] on /usr/lib64/libcrypto.so.0.9.8 <= /usr/lib64/libcurl.so.3.0.0
> ldd[02] on /usr/lib64/libcrypto.so.6 <= /usr/bin/git
The answer is here. git was obviously built against a different version
of OpenSSL than curl. This is an OpenSUSE problem.
Mike
prev parent reply other threads:[~2008-02-08 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 9:46 Why does git depend on two versions of libcrypto? H.Merijn Brand
2008-02-08 10:03 ` Mike Hommey [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=20080208100346.GA20601@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=h.m.brand@xs4all.nl \
/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).