Specially, pay attention to INSTALLATION DIRECTORY and GEM PATH "install" => "-no-ri -no-rdoc -env-shebang" ![]() RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8 When installing a gem, if it fail, please take a closer look to the output Not compatible with the platform (see Gem List for compatibility) or Either the gem requireĬompilation, which means the installation of Development Kit, the gem is There might be lot of reasons why it could fail. For some strange reason, it fails to install gems. Just re-run the DevKit installation, using the -force switch if necessary After upgrading to Windows 8 Customer Preview, the DevKit doesn't work anymore. Out any 32bits application running on Windows 圆4 bits due the automatic file Looks like folder looses the proper permissions and is locking This is not a Ruby or RubyInstaller issue but instead one from incorrectĪnother source of this issue could be the installation of either Cygwin or Some details (under the manual section) to fix the issue.Īnother alternative, while radical, is format the NTFS harddrive where Ruby Upgraded from previous Release Candidate to RTM versions. Users facing this issue are Windows 7 Ultimate (32bits) that in the majority There has been reports of users unable to install any gem unless UAC isĭisabled or the command prompt is executed as Administrator. You can read more about this issue on this thread Can't install gems due Errno::EEXIST errors under Windows 7 Please check that no leftover of your cygwin install remains in your homeĭirectory, specially any. Installed in the system are affected during installation of gems that require ![]() We discovered that under some scenarios, users that previously had Cygwin ![]() When compiling gems, it complained about missing ruby.h file Note: Please remember this option will only affect new Command Prompt Need to select the correct option during installation: If you want this particular version of Ruby be available everywhere, you will ] Not recognized as an internal or external command, operable program or batch fileīy default, RubyInstaller will not alter the PATH used by the system toįind applications/executables. Please feel free to add your ownįor further help, refer to the RubyInstaller mailing list Here you'll find a list of the common issues some users have experienced and Having a problem when installing or using RubyInstaller? Life is full of
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |