Thanks Damian ! We will try to fix the path issue for the next release.
Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, April 4, 2012 at 9:55 AM, Damian Monogue wrote: > I have been having the same problem with running the buildr all-in-one > under solaris. When I finally gave up on that approach, I tried installing > jruby 1.6.7 and installing buildr from there... and that's when I ran into > further issues. > > So, for those trying to run buildr under solaris and having problems, here > is what eventually worked for me: > > Install jruby 1.6.5.1 . Do not use 1.6.6 or 1.6.7, as they have a > regression which causes gems to not install properly on the system. The > Jruby jira issue in particular that pointed me to this issue was: > https://jira.codehaus.org/browse/JRUBY-6494 . > > I installed jruby to my home directory, but you could of course install it > systemwide if you chose to. I was then able to properly `gem install > buildr` and get working. > > On a somewhat unrelated note, the jgem script being carried in the buildr > all-in-one bundle has a hardcoded path for what I can only assume is Alex's > machine, given the path in question. May be worthwhile to clean that up > before the next release. (BUILDR-633 was created to track this). > > > > > > > That sounded like a great solution but it doen't work either. I'm cursed . > . > > . > > > > $ buildr clean build > > FFI::NCurses: "newscr" not defined > > FFI::NCurses: "ESCDELAY" not defined > > LoadError: no such file to load -- > > rspec/core/extensions/instance_eval_with_args > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-core-2.1.0/lib/rspec/core/extensions.rb:3 > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-core-2.1.0/lib/rspec/core/extensions.rb:1 > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-core-2.1.0/lib/rspec/core.rb:1 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-2.1.0/lib/rspec.rb:1 > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-core-2.1.0/lib/rspec/core/formatters/helpers.rb:1 > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/rspec-core-2.1.0/lib/rspec/core/formatters/base_formatter.rb:36 > > require at org/jruby/RubyKernel.java:1038 > > require at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/buildr-1.4.6-java/lib/buildr.rb:36 > > (root) at > > /opt/buildr-1.4.6/lib/ruby/gems/1.8/gems/buildr-1.4.6-java/bin/buildr:18 > > load at org/jruby/RubyKernel.java:1063 > > (root) at /opt/buildr-1.4.6/bin/_buildr:19 > > > > On Wed, Oct 19, 2011 at 10:55 AM, Alex Boisvert <[email protected] > > (mailto:[email protected]) > > wrote: > > > > > Maybe the easier way is to install the "all-in-one" distro, > > > http://rubyforge.org/frs/?group_id=3180 > > > > > > Just untar the distribution somewhere and create an alias for "buildr" > that > > > points to $BUILDR_HOME/bin/buildr, or add to your PATH. > > > > > > alex > > > > > > > > > On Wed, Oct 19, 2011 at 7:09 AM, Line, Steve <[email protected] > > > (mailto:[email protected]) > > > > wrote: > > > > > > > > > > Thanks Alex. > > > > > > > > > > > > On Tue, Oct 18, 2011 at 4:14 PM, Alex Boisvert <[email protected] > > > > (mailto:[email protected]) > > > > > wrote: > > > > > > > > > > > > > Hi Steve, > > > > > > > > > > I would start by upgrading either your system Ruby to use the latest > > > > > Rubygems: > > > > > http://docs.rubygems.org/read/chapter/3#page14 > > > > > > > > > > > > > > > > > > > > > I've run both > > > > gem update --system > > > > and > > > > ruby -S gem update --system > > > > with my path pointing to normal ruby > > > > and > > > > jruby -S gem update --system > > > > with my path pointing to jruby > > > > > > > > They both say that ruby gems is up to date: > > > > > > > > ruby is in /opt/csw/bin below > > > > > > > > # echo $PATH > > > > /opt/csw/gcc3/bin:/opt/csw/bin:/usr/local/bin:/usr/sbin:/usr/bin:. > > > > # ruby -S gem update --system > > > > Latest version currently installed. Aborting. > > > > # gem update --system > > > > Latest version currently installed. Aborting. > > > > > > > > and for jruby: > > > > # echo $PATH > > > > > > > > > > > > > > /opt/jruby/jruby-1.1.4/bin:/opt/csw/bin:/usr/local/bin:/usr/sbin:/usr/bin:. > > > > # jruby -S gem update --system > > > > Updating RubyGems > > > > Nothing to update > > > > > > > > > > > > > > > > > > Or upgrade your JRuby installation to a recent version (1.6.x+). > > > > > > > > > > Once you have recent versions of JRuby/Rubygems, I think your buildr > > > > > installation should go much smoother. > > > > > > > > > > > > > Ok, I'll try updating jruby next, as I said to Rhett. Is there a quick > > > > > > > > > > way > > > > to do this? > > > > > > > > -- > > > > Steven Line > > > > 303-215-0131 > > > > RedPrairie > > > > Denver, CO > > > > > > > > Email Disclaimer: > > > > http://www.redprairie.com/emaildisclaimer/ > > > > > > > > > > > > > > > > > > > > -- > > Steven Line > > 303-215-0131 > > RedPrairie > > Denver, CO > > > > Email Disclaimer: > > http://www.redprairie.com/emaildisclaimer/ > > > > >
