From: Lazaridis Ilias <ilias@...>
Date: 2011-07-02T15:38:57+09:00
Subject: [ruby-core:37731] [Ruby 1.9 - Bug #4941] cannot load such file -- rubygems.rb (LoadError)


Issue #4941 has been updated by Lazaridis Ilias.


Nobuyoshi Nakada wrote:
> It doesn't sound like an unreasonable limit to need to be installed before running, on many platforms, shared libraries are loaded from fixed paths.
> I don't want to include the workaround since it is not used after installation at all.

Please forget about the condition "installed".

This issue is about the condition "compiled". About the behaviour of the ruby-interpreter within the source-tree, right after the compilation.

* Rubygems should not *block* the freshly compiled interpreter from working within the source tree.

I'm not asking to include a workaround, but to resolve this issue in some production-quality manner.

Specification should be:

* Status compiled : interpreter works as-is within the source-tree
* Status installed: interpreter depends on directories specified during the installation
----------------------------------------
Bug #4941: cannot load such file -- rubygems.rb (LoadError)
http://redmine.ruby-lang.org/issues/4941

Author: Lazaridis Ilias
Status: Rejected
Priority: Normal
Assignee: Usaku NAKAMURA
Category: core
Target version: 
ruby -v: ruby 1.9.3dev (2011-06-28 trunk 32265) [i386-mswin32_90]


=begin

From within the directory of a fresh trunk checkout:

$ win32\configure
$ nmake
$ miniruby -e"p 'hello'" #=> hello
$ ruby -e"p 'hello'"

 <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError)
        from <internal:gem_prelude>:1:in `<compiled>'

(the exact same procedure using branch 1.9.2 worked fine)
=end



-- 
http://redmine.ruby-lang.org