Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <1BF5226F-4D8A-406F-9898-6AC432C736ED@detailedbalance.net>
References: 
 <CAF4LrSiNp3oFoejVmcRjqHJLeAQ_7OYU5WWTQYLY9g7yKpAA1Q@mail.gmail.com>
	<1BF5226F-4D8A-406F-9898-6AC432C736ED@detailedbalance.net>
Date: Wed, 19 Oct 2011 07:59:19 -0600
Message-ID: 
 <CAF4LrSi0kbjPPHhE0DLEb7Bxe5NV06DPNnL2=An_EZLVsq5D6Q@mail.gmail.com>
Subject: Re: Trying to update buildr on Solaris 10
From: "Line, Steve" <steve.line@redprairie.com>
To: users@buildr.apache.org
Content-Type: multipart/alternative; boundary=001485f9f3dc1cd36204afa73fb6

--001485f9f3dc1cd36204afa73fb6
Content-Type: text/plain; charset=ISO-8859-1

Thanks Rhett . . . see below


> I'm having fits trying to update buildr on a Solaris 10 box. Can't get it
> to
> > work with ruby or jruby.
> >
> > I updated ruby to 1.8.7 and when I run gem update builr I get:
> >
> > -bash-3.00# gem update buildr
> > Updating installed gems
> > Nothing to update
> > -bash-3.00# buildr --version
> > Buildr 1.3.3 (JRuby 1.1.4)
>
> It looks like the `buildr` executable on your path is using JRuby. You
> could confirm this with `which buildr`. If so, updating the plain ruby
> version will have no effect on what happens when you run `buildr`. You could
> try running the ruby version using `ruby -S buildr` to see if you get a
> different result.
>

You are correct that I'm currently using the jruby version of buildr:

-bash-3.00# which buildr
/opt/jruby/jruby-1.1.4/bin/buildr

And there is apparently no ruby version of buildr:

-bash-3.00# ruby -S buildr --version
/opt/csw/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:247:in `to_specs':
Could not find buildr (>= 0) amongst [Antwrap-0.7.0-java,
archive-tar-minitar-0.5.2, builder-2.1.2, ci_reporter-1.5.1, highline-1.5.1,
highline-1.4.0, hoe-2.3.3, hoe-1.8.0, hoe-1.6.0, jruby-openssl-0.3,
jruby-openssl-0.2, json_pure-1.4.3, net-sftp-2.0.4, net-sftp-2.0.1,
net-ssh-2.0.23, net-ssh-2.0.4, net-ssh-2.0.3, rake-0.8.7, rake-0.8.3,
rake-0.8.1, rspec-1.1.8, rspec-1.1.4, rubyforge-2.0.3, rubyforge-1.0.0,
rubygems-update-1.8.11, rubyzip-0.9.4, rubyzip-0.9.1, xml-simple-1.0.11]
(Gem::LoadError)
        from /opt/csw/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:256:in
`to_spec'
        from /opt/csw/lib/ruby/site_ruby/1.8/rubygems.rb:1210:in `gem'
        from /opt/jruby/jruby-1.1.4/bin/buildr:18

So I tried ruby -S gem install buildr (as root) and got more trouble:

-bash-3.00# ruby -S gem install buildr
Building native extensions.  This could take a while...
ERROR:  Error installing buildr:
        ERROR: Failed to build gem native extension.

        /opt/csw/bin/ruby18 extconf.rb
checking for jni.h... yes
checking for dl.h... yes
checking for locale_charset() in iconv.h... no
checking for nl_langinfo() in langinfo.h... yes
checking for setlocale() in locale.h... yes
checking for getenv()... yes
creating extconf.h
creating Makefile

make
javah -classpath ../data/rjb jp.co.infoseek.hp.arton.rjb.RBridge
/opt/SUNWspro/bin/cc -I. -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I.
-I"/usr/jdk/latest/include" -I"/usr/jdk/latest/include/solaris"
-DRUBY_EXTCONF_H=\"extconf.h\" -I/opt/csw/include -D_FILE_OFFSET_BITS=64
-I/opt/csw/include -KPIC -xO3 -m32 -xarch=386  -KPIC
-I"/usr/jdk/latest/include" -I"/usr/jdk/latest/include/solaris"  -c load.c
"jniwrap.h", line 17: warning: invalid white space character in directive
"jniwrap.h", line 18: warning: invalid white space character in directive
"jniwrap.h", line 19: warning: invalid white space character in directive
"jniwrap.h", line 21: warning: invalid white space character in directive
"jniwrap.h", line 23: warning: invalid white space character in directive
"jniwrap.h", line 25: warning: invalid white space character in directive
"jniwrap.h", line 27: warning: invalid white space character in directive
"jniwrap.h", line 29: warning: invalid white space character in directive
"jniwrap.h", line 31: warning: invalid white space character in directive
"jniwrap.h", line 32: warning: invalid white space character in directive
"load.c", line 111: warning: statement not reached
"load.c", line 215: undefined symbol: ARCH
"load.c", line 215: warning: improper pointer/integer combination: arg #1
"load.c", line 264: warning: assignment type mismatch:
        pointer to void "=" pointer to function(pointer to pointer to const
struct JNINativeInterface_ {pointer to void reserved0, pointer to void
reserved1, pointer to void reserved2, pointer to void reserved3, pointer to
function(..) returning int GetVersion, pointer to function(..) returning
pointer to struct _jobject {..} DefineClass, pointer to function(..)
returning pointer to struct _jobject {..} FindClass, pointer to function(..)
returning pointer to struct _jmethodID {..} FromReflectedMethod, pointer to
function(..) returning pointer to struct _jfieldID {..} FromReflectedField
<these errors continued for a long ways>


> >
> >
> > If I use jruby I get this:
> >
> > -bash-3.00# jruby -S gem update buildr
> > Updating installed gems
> > ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
> >    bad response Found 302 (http://gems.rubyforge.org/latest_specs.4.8)
> >
> > -bash-3.00# jruby -S gem update buildr  --source http://rubygems.org
> > Updating installed gems
> > ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
> >    bad response Found 302 (http://rubygems.org/latest_specs.4.8)
> >
> > Could somebody offer some help?  I don't care whether we use jruby or
> ruby I
> > just want buildr to update and work.
>
> This is a rubygems problem. The version of JRuby you have installed (1.1.4)
> is very old (August 2008). Apparently the rubygems library that's included
> with it doesn't work with rubygems.org as it is today. Can you upgrade to
> a more recent version of JRuby? (AFAIK, you can't upgrade rubygems alone on
> JRuby.) Alternatively, you might be able to download the buildr gem
> directly[1] and install it from the file, but I don't know that the current
> version of buildr will work with a JRuby that's that old.
>
>
Thanks Rhett. I'll try updating the jruby this morning and see how far I
get.  I tried downloading the buildr gem directly and it needed dependencies
so after manually downloading and installing two dependencies it seemed
never ending so I put that technique on hold.


-- 
Steven Line
303-215-0131
RedPrairie
Denver, CO

Email Disclaimer:
http://www.redprairie.com/emaildisclaimer/

--001485f9f3dc1cd36204afa73fb6--