Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Cannot locate dyld's (libc) when using jruby with boxen/puppet-java shim #23

Closed
robbiegill opened this issue Jul 5, 2013 · 1 comment · Fixed by #37
Closed

Cannot locate dyld's (libc) when using jruby with boxen/puppet-java shim #23

robbiegill opened this issue Jul 5, 2013 · 1 comment · Fixed by #37

Comments

@robbiegill
Copy link

When I try to run a jruby app it cannot locate libc.dyld

I originally left details here : boxen/puppet-ruby#14 (comment)

Essentially it seems the java shim sets $DYLD_FALLBACK_LIBRARY_PATH to help find homebrew libs, but it my experience it means it cannot find the libs in /usr/local.

I can manually export DYLD_LIBRARY_PATH=/usr/lib and then jruby finds libc again, but as noted in the other thread - there are some weird osx issues if setting a DYLD env variable.

Before using boxen I didn't seem to have any issue with jruby finding gcc installed through homebrew, but I sure there's a reason for the shim setting the DYLD path.

For now I've removed the shim from the path so that it falls back to /usr/bin/java and haven't noticed any side-effects yet.

Thoughts - ideas?

Thanks

@zachpendleton
Copy link

Having this same problem - some kind of standard solution would be nice.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants