-
Notifications
You must be signed in to change notification settings - Fork 68
how this happened #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Somehow the gem didn't install correctly in your environment. I really don't know what other advice to give you at this point. |
I'm experiencing the same error. |
Have you used RVM? (rvm.io) |
I'm familiar with RVM but I haven't done anything with it so far - what should I do with it? Switch Ruby versions? |
|
In my opinion, if you aren't using RVM, you don't yet have Ruby installed. You should never use the system Ruby for user operations. The system Ruby is for the system. RVM gives you a Ruby for you to use (for development, personal use, etc). On top of that, it sets up Ruby gems correctly so you don't get strange path errors. (Many systems install Ruby incorrectly and therefore can't install gems correctly...it's just a thing I've observed). |
You setup RVM, then set the default Ruby to something other than system. Then, when you start a shell, life is good. I recommend this guide: (useful even if you don't use Ubuntu) (I am planning to write a better guide for RVM. I'm just very tied up at the moment. I full recognize that the instructions from rvm.io leave a lot be desired). |
Thanks, I'm installing now. I was actually using the prerelease gem and getting the same error as in the original issue. |
👍 I look forward to hearing how it goes. We'll get through this, that's for sure. |
@mojavelinux Same error, after using the nvm installed version of Ruby (2.2.6):
|
Installation worked fine, I get the error when trying to run |
Can you run |
This is a clear case of a mixed up Ruby environment. It really doesn't have anything to do with this gem. You have binstubs that aren't in sync with the Ruby environment you are using. You'll face this same thing with any gem you try to use. I intend to write a guide that explains how to get gems installed correctly so that you can use them without errors. Let's take it up there. See asciidoctor/asciidoctor.org#399 |
C:/Ruby21-x64/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
'require': cannot load such file -- C:/Ruby21-x64/lib/ruby/gems/2.1.0/gems/asciidoctor-epub3-1 .5.0.dev/bin/../lib/asciidoctor-epub3 (LoadError) from C:/Ruby21-x64/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
require'from C:/Ruby21-x64/lib/ruby/gems/2.1.0/gems/asciidoctor-epub3-1.5.0.dev/bin/asciidoctor-epub3:3:in
<top (required)>' from C:/Ruby21-x64/bin/asciidoctor-epub3:23:in
load'from C:/Ruby21-x64/bin/asciidoctor-epub3:23:in `
The text was updated successfully, but these errors were encountered: