[MacPorts] #19122: OpenSSL 1.0.0-beta1 breaks packages that expect libcrypto.0.9.8

[watson]

I am rather ignorant of these things. (like I said, I only installed
macports recently) But this is what happens when I run git:

packages% git
dyld: Library not loaded: /opt/local/lib/libcrypto.0.9.8.dylib
  Referenced from: /opt/local/bin/git
  Reason: image not found
Trace/BPT trap

Is the solution to blow away my current git and then re-install it?
Will MP take care of noticing that i now have OpenSSL v1 instead of
what it was before and deal with it automatically?



On Thu, Jul 29, 2010 at 8:24 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Jul 29, 2010, at 20:41, watson wrote:
>
>> i'm struggling with getting OpenSSL to play nice with other ports.
>> below is a response by ryan to my comments on this ticket:
>>
>> http://trac.macports.org/ticket/19122#comment:18
>>
>> in summary, here's what happened: In trying to install Matplotlib
>> (python plotting util)... i ran into trouble with wxWidgets-python
>> failing. Someone posted a workaround involving installing Mesa which I
>> followed here:
>> http://www.mail-archive.com/macports-users@lists.macosforge.org/msg19905.html
>>
>> Apparently, in the process of doing this I screwed up (by upgrading?)
>> OpenSSL, which breaks a lot of things I use including Git it seems.
>>
>> I am unclear how to proceed from this point. should I force a
>> downgrade of OpenSSL? Or is it possible that there are other versions
>> of the components (such as cURL, git, python) that can all use OpenSSL
>> v1.0.0a? I am incredulous since it is only in the last month that
>> installed MacPorts on my machine.
>
> You should tell us what specific problems you're having that you believe are caused by openssl 1.0.0a. We have already fixed many such problems, so if there are more, let's hear about them so we can fix them too.
>
> For example, in what way do you believe openssl 1.0.0a is breaking git, curl, and python?
>
>