Thanks for all the help and advices! New therubyracer 0.9.0 gem did the trick. Still don't know the reason of such behaviour.
2011/5/29 Matthew Smart <[email protected]>: > Hey, > I managed to reproduce your problem with therubyrhino not being recognized, > and I went on to test the mustang engine, and that causes the ExecJS > framework to crash outright. I believe this may be a problem more related to > ExecJS, you will likely get some better help over on the ExecJS Issues > board, here: https://github.com/sstephenson/execjs/issues > Good Luck! > > On Fri, May 27, 2011 at 9:43 PM, Andrey Voronkov <[email protected]> > wrote: >> >> changed gem 'therubyracer' to gem 'therubyrhino' >> run bundle update >> >> Got this: >> >> in `<module:ExecJS>': Could not find a JavaScript runtime. See >> https://github.com/sstephenson/execjs for a list of available >> runtimes. (ExecJS::RuntimeUnavailable) >> >> 2011/5/28 Matthew Smart <[email protected]>: >> > therubyrhino >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-core?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
