search

scttnlsn / dandelion

Incremental Git repository deployment.
http://scttnlsn.github.io/dandelion
MIT License
738 stars 60 forks source link

dyld: lazy symbol binding failed: Symbol not found: _SSL_load_error_strings #129

Closed lightfuze closed 9 years ago

lightfuze commented 9 years ago

I get the following when trying to run any dandelion command:

dyld: lazy symbol binding failed: Symbol not found: _SSL_load_error_strings
  Referenced from: /Library/Ruby/Gems/2.0.0/gems/rugged-0.22.2/lib/rugged/rugged.bundle
  Expected in: flat namespace

dyld: Symbol not found: _SSL_load_error_strings
  Referenced from: /Library/Ruby/Gems/2.0.0/gems/rugged-0.22.2/lib/rugged/rugged.bundle
  Expected in: flat namespace

Trace/BPT trap: 5

OS X 10.10.3 dandelion 0.4.13

scttnlsn commented 9 years ago

Not sure if this was a regression. Could you try v0.4.10 as well?

lightfuze commented 9 years ago

0.4.10 also installed rugged-0.21.4, but i'm getting the same result

TheLonelyGhost commented 9 years ago

Hold up, this says you're running rugged v0.22.2, but the manifest for dandelion 0.4.13 requires rugged v0.22.1b1. Perhaps this is a problem with the way rubygems is resolving versions? When you install dandelion 0.4.10 or 0.14.13, open an IRB session and run the following:

require 'dandelion'

puts Rugged::VERSION

EDIT: derp, pessimistic operator fail.

If both produce "0.22.2", try running gem install rugged -v0.22.1b1 and running dandelion. Might be an issue with that release of rugged.

lightfuze commented 9 years ago

Installing rugged -v0.22.1b1 and uninstalling the other versions did the trick. dandelion 0.4.13 is working!

scttnlsn commented 9 years ago

@lightfuze So was this an issue specific to your setup or is there an issue with Dandelion? If there's an issue can you outline the steps I can take to reproduce it?

lightfuze commented 9 years ago

@scttnlsn I recently did a gem update; I had been on dandelion -v0.4.6. After that is when I noticed the issue. I think this was probably not a dandelion issue, but possibly due another version of rugged that didn't want to play.

scttnlsn commented 9 years ago

Okay, thanks. Re-open this issue if you encounter the problem again.

TheLonelyGhost commented 9 years ago

@scttnlsn This actually seems to be a bug with the gemspec definition. Would require further testing to ensure compatibility with rugged v0.22.2 because '0.22.2' matches the '~> 0.22.1b1' version specifier.

If it is not compatible, perhaps a dandelion patch version should be bumped (and 0.4.13 yanked) to also specify '< 0.22.2' for rugged?

scttnlsn commented 9 years ago

@TheLonelyGhost Yeah, you're right. Here's the Rugged issue for this: https://github.com/libgit2/rugged/issues/475

I'll update the Gemspec and push a new version for now.

Thanks!