You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I try to run it with sudo I get this, even I have the 'event machine' gem properly installed
sudo ruby siriServer.rb
/Users/nybras/.rvm/rubies/ruby-1.9.2-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': no such file to load -- eventmachine (LoadError)
from /Users/nybras/.rvm/rubies/ruby-1.9.2-head/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from siriServer.rb:2:in `<main>'
and without sudo
ruby siriServer.rb
/Users/nybras/.rvm/gems/ruby-1.9.2-head/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_tcp_server': no acceptor (RuntimeError)
from /Users/nybras/.rvm/gems/ruby-1.9.2-head/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in `start_server'
from siriServer.rb:73:in `block in <main>'
from /Users/nybras/.rvm/gems/ruby-1.9.2-head/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `call'
from /Users/nybras/.rvm/gems/ruby-1.9.2-head/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
from /Users/nybras/.rvm/gems/ruby-1.9.2-head/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
from siriServer.rb:72:in `<main>'
why not to keep the #!/usr/bin/env ruby
and run this instead
rvm use 1.9.2 --default
This should set you default ruby 1.9.2 if you have the ruby 1.9.2 already installed in the rvm
and to run the server using (rvmsudo ruby siriProxy.rb)
use rvmsudo not sudo
also when installing gems use rvmsudo gem install "the gem name"
This could help: http://www.stantheripper.com/siri/
I use RVM, so I removed the
and replaced with
when I try to run it with sudo I get this, even I have the 'event machine' gem properly installed
and without sudo
I dont know what to do from now on, I was following this tutorial:
http://f3v3r.com/2011/12/29/how-to-get-iphone-4s-siri-authentication-keys/
The text was updated successfully, but these errors were encountered: