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.
When I try to run a jruby app it cannot locate libc.dyld
I originally left details here : https://github.com/boxen/puppet-ruby/pull/14#issuecomment-20504734
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