jopenssl?

164 views
Skip to first unread message

Kevin

unread,
Jul 20, 2010, 3:43:59 PM7/20/10
to Grackle Development
Moderators, I just posted a question a few moments ago but realized my
own mistake. No need to publish the previous one. I had ruby 1.8 and
1.9 installed and was apparently crossing streams with my gems. I
removed 1.8 completely and am now on 1.9.

I decided to pull down grackle manually and just run the tests. This
should help ensure I have a proper setup.

If I navigate into the test directory and invoked the test as:
ruby test_client.rb

I get the following. Is this normal? I have installed jruby-openssl.
Is there another gem that I am missing. If I try gem install jopenssl
or openssl, I don't find anything. Here's the stack.

/var/lib/gems/1.9.0/gems/jruby-openssl-0.7/lib/openssl.rb:61:in
`require': no such file to load -- jopenssl (LoadError)
from /var/lib/gems/1.9.0/gems/jruby-openssl-0.7/lib/openssl.rb:61:in
`<top (required)>'
from /usr/lib/ruby/1.9.0/net/https.rb:102:in `require'
from /usr/lib/ruby/1.9.0/net/https.rb:102:in `<top (required)>'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth/consumer.rb:2:in
`require'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth/consumer.rb:2:in
`<top (required)>'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth/client/helper.rb:
2:in `require'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth/client/helper.rb:
2:in `<top (required)>'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth.rb:10:in
`require'
from /var/lib/gems/1.9.0/gems/oauth-0.4.1/lib/oauth.rb:10:in `<top
(required)>'
from /home/mrjabba/dev/ruby/grackle/lib/grackle.rb:24:in `require'
from /home/mrjabba/dev/ruby/grackle/lib/grackle.rb:24:in `<top
(required)>'
from /home/mrjabba/dev/ruby/grackle/test/test_helper.rb:3:in
`require'
from /home/mrjabba/dev/ruby/grackle/test/test_helper.rb:3:in `<top
(required)>'
from test_client.rb:1:in `require'
from test_client.rb:1:in `<main>'

My local gems

*** LOCAL GEMS ***

addressable (2.1.2)
appengine-apis (0.0.18)
appengine-rack (0.0.11)
appengine-sdk (1.3.5)
appengine-tools (0.0.15)
bundler08 (0.8.5)
dm-appengine (0.1.0)
dm-core (1.0.0)
extlib (0.9.15)
gemcutter (0.6.1)
google-appengine (0.0.15)
grackle (0.1.10)
haml (3.0.13)
jruby-jars (1.5.1)
jruby-openssl (0.7)
jruby-rack (1.0.1)
json (1.4.3)
lexidecimal (0.0.1)
mime-types (1.16)
oauth (0.4.1)
rack (1.2.1)
rubyzip (0.9.4)
sinatra (1.0)


ruby 1.9.0 (2008-10-04 revision 19669) [x86_64-linux]

gem version 1.3.5

I'm running Ubuntu Lynx 64 bit.

Thanks for any info you can provide. Sorry if this is a ridiculously
easy ruby question.

Kevin


Hayes Davis

unread,
Jul 21, 2010, 12:20:16 PM7/21/10
to grac...@googlegroups.com
Kevin,

Unfortunately I'm not at all familiar with the ins and outs of jruby
or app engine. However, a thread[1] on the JRuby and App Engine group
seems to imply that jruby-openssl won't work on Google App Engine and
so you can't use net/http to do HTTPs requests on that platform. If
that's the case, using grackle there would require a patch to grackle
and probably to the oauth gem as well to use an app-engine-approved
https library.

Hayes

[1] http://groups.google.com/group/appengine-jruby/browse_thread/thread/6b62a4418fde5c4d/40e17135ec22e34e?lnk=raot

Kevin

unread,
Jul 21, 2010, 7:22:33 PM7/21/10
to Grackle Development
Thanks for the reply. I'll proceed with caution regarding appengine
then.

But, I was getting this error message just by trying to run one of the
unit tests as well, absent of any appengine activity.

> > If I navigate into the test directory and invoked the test as:
> > ruby test_client.rb

Perhaps it's a config issue on my part. I will continue to dig and
post back if I figure it out.

thanks!
Kevin


On Jul 21, 11:20 am, Hayes Davis <ha...@appozite.com> wrote:
> Kevin,
>
> Unfortunately I'm not at all familiar with the ins and outs of jruby
> or app engine. However, a thread[1] on the JRuby and App Engine group
> seems to imply that jruby-openssl won't work on Google App Engine and
> so you can't use net/http to do HTTPs requests on that platform. If
> that's the case, using grackle there would require a patch to grackle
> and probably to the oauth gem as well to use an app-engine-approved
> https library.
>
> Hayes
>
> [1]http://groups.google.com/group/appengine-jruby/browse_thread/thread/6...
Reply all
Reply to author
Forward
0 new messages