You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: