First spike at jruby

[wfarr]

No description provided.

[wfarr]

Failing to build but only inside the Puppet run:

g++ -O2 -Wall  -I'/opt/boxen/rbenv/versions/jruby-1.7.3/include'   -c unixlauncher.cpp -MMD -MP -MF build/unix/Darwin/unixlauncher.o.d -o build/unix/Darwin/unixlauncher.o
g++ -O2 -Wall  -I'/opt/boxen/rbenv/versions/jruby-1.7.3/include'  -L'/opt/boxen/rbenv/versions/jruby-1.7.3/lib'   -o build/unix/Darwin/jruby-launcher build/unix/Darwin/argparser.o build/unix/Darwin/utilsfuncs.o build/unix/Darwin/ng.o build/unix/Darwin/strlcpy.o build/unix/Darwin/jrubyexe.o build/unix/Darwin/unixlauncher.o -lstdc++
cp build/unix/Darwin/jruby-launcher jruby
/opt/boxen/rbenv/versions/jruby-1.7.3/bin/jruby -S rake
/opt/boxen/rbenv/versions/jruby-1.7.3/bin/jruby -S rspec ./spec/launcher_spec.rb
jruby: No such file or directory -- rspec (LoadError)
rake aborted!
/opt/boxen/rbenv/versions/jruby-1.7.3/bin/jruby -S rspec ./spec/launcher_spec.rb failed
/opt/boxen/repo/.bundle/ruby/1.8/gems/rspec-core-2.12.2/lib/rspec/core/rake_task.rb:156:in `run_task'
/opt/boxen/repo/.bundle/ruby/1.8/gems/rspec-core-2.12.2/lib/rspec/core/rake_task.rb:124:in `initialize'
org/jruby/RubyBasicObject.java:1683:in `__send__'
org/jruby/RubyKernel.java:2107:in `send'
/opt/boxen/repo/.bundle/ruby/1.8/gems/rspec-core-2.12.2/lib/rspec/core/rake_task.rb:122:in `initialize'
org/jruby/RubyProc.java:249:in `call'
org/jruby/RubyArray.java:1613:in `each'
org/jruby/RubyArray.java:1613:in `each'
org/jruby/RubyArray.java:1613:in `each'
org/jruby/RubyKernel.java:1046:in `load'
Tasks: TOP => default => spec
(See full trace by running task with --trace)

[wfarr]

Hurray for relative bin resolution in the JRuby build process. Sigh.

/cc @benburkert

[brntbeer]

ping @benburkert again

[henry74]

Looking for clarification - is JRUBY currently not supported through Boxen?

[robbiegill]

Not sure if this is the right thread, but I have issues with jruby running on a boxen java machine.

Problems stem from DYLD_FALLBACK_LIBRARY_PATH set in /opt/boxen/bin/java

bundle or starting a jruby app fail to find libc.dyld unless I export DYLD_LIBRARY_PATH=/usr/lib. Not so bad, but it seems there is an osx issue that gives errors like this dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid any time a setuid or setgid command is run (e.g. sudo, ps) - so that becomes annoying.

Any ideas - other than removing boxen-java and doing java manually? Maybe this belongs in the boxen-java repo?

Thanks

᚛ $ more `which java`
#!/bin/sh
#
# Invoke java with the $DYLD_LIBRARY_PATH set with the homebrew lib dir.
# This allows java to load native libraries installed via homebrew.

export DYLD_FALLBACK_LIBRARY_PATH="$BOXEN_HOME/homebrew/lib:$DYLD_FALLBACK_LIBRARY_PATH"

if [ -x /usr/libexec/java_home ]; then
  export JAVA_HOME=`/usr/libexec/java_home`
fi

exec /usr/bin/java "$@"

[henry74]

This is deprecated. Use rbenv to install jruby through boxen-rbenv. Should work for you then, although the latest jruby wasn't available - just 1.7.3

[robbiegill]

Hmm. That's how I installed jruby - through rbenv install jruby-1.7.3.

So it seems my issue might be with boxen/puppet-java in that the java shim
is setting that env variable (it says to help find libs installed through
homebrew) but in my case seems to not find libs in /usr/lib

Maybe I'll cross post there unless you have any other ideas? Thanks.
On Jul 5, 2013 9:42 AM, "Henry Hwangbo" [email protected] wrote:

This is deprecated. Use rbenv to install jruby through boxen-rbenv. Should
work for you then, although the latest jruby wasn't available - just 1.7.3

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/14#issuecomment-20528158
.

[ocxo]

Looks like the best way to get jruby in boxen is via rbenv for now.