# ...rubygems... in require: no such file to load

**URL:** <https://www.ruby-forum.com/t/rubygems-in-require-no-such-file-to-load/49759>\
**Category:** Ruby\
**Created:** [December 8, 2005, 2:42pm UTC](https://www.ruby-forum.com/t/rubygems-in-require-no-such-file-to-load/49759 "2005-12-08T14:42:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wybo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/cc9497/32.png) [@wybo](https://www.ruby-forum.com/u/wybo)\
**Post date:** [December 8, 2005, 2:42pm UTC](https://www.ruby-forum.com/t/rubygems-in-require-no-such-file-to-load/49759/1 "2005-12-08T14:42:42Z")

</div>

I have a script requiring rubygems, rio, and more, plus a module in a  
non-standard directory. It works fine on my machine, but not on the  
machine of a friend.

Here’s the important part of my module  
require ‘session’  
require ‘rubygems’  
require ‘term/ansicolor’

```
class String
  include Term::ANSIColor
end

module TestMe
  def sys(command)
    ...
  end
end # TestMe

```

It is stored in /home/local/ruby/testme.rb  
And this is the calling script:

```
#!/usr/bin/ruby
puts 'LOAD_PATH:',$LOAD_PATH.join("\n")
puts 'RUBYLIB:',ENV['RUBYLIB']
puts 'RUBYOPT:',ENV['RUBYOPT']

require 'rubygems'
require 'rio'
require 'testme'
include TestMe
sys('ls')

puts rio('/etc/passwd').gets

```

On my machine it successfully says:

```
tmp>testme
LOAD_PATH:
.
/home/local/ruby
/usr/local/lib/ruby/site_ruby/1.8
/usr/local/lib/ruby/site_ruby/1.8/i686-linux
/usr/local/lib/ruby/site_ruby
/usr/local/lib/ruby/1.8
/usr/local/lib/ruby/1.8/i686-linux
.
RUBYLIB:
.:/home/local/ruby
RUBYOPT:
nil
system call: ls successful
root:x:0:0:root:/home/root:/bin/bash
tmp>

```

But on the friend’s machine (who stores the module in  
/home/rrt/local/lib/site\_ruby/1.8):

```
tmp>testme
LOAD_PATH:
/home/rrt/local/lib/site_ruby/1.8/i386-linux
/home/rrt/local/lib/site_ruby/1.8
/usr/local/lib/site_ruby/1.8
/usr/local/lib/site_ruby/1.8/i386-linux
/usr/local/lib/site_ruby
/usr/lib/ruby/1.8
/usr/lib/ruby/1.8/i386-linux
.
RUBYLIB:
/home/rrt/local/lib/site_ruby/1.8/i386-linux:/home/rrt/local/lib/site_ruby/1.8
RUBYOPT:
nil
/usr/lib/ruby/1.8/rubygems/custom_require.rb:26:in `require': No 

```

such file  
to load – testme (LoadError)  
from ./testme:8

What’s wrong? Something with the rubygems installation?

---

<div class="post-metadata">

**Author:** ![wybo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/cc9497/32.png) [@wybo](https://www.ruby-forum.com/u/wybo)\
**Post date:** [December 8, 2005, 4:58pm UTC](https://www.ruby-forum.com/t/rubygems-in-require-no-such-file-to-load/49759/2 "2005-12-08T16:58:40Z")

</div>

wybo wrote:

> I have a script requiring rubygems, rio, and more, plus a module in a  
> non-standard directory. It works fine on my machine, but not on the  
> machine of a friend.

[…]

> ```
> /usr/lib/ruby/1.8/rubygems/custom_require.rb:26:in `require': No 
> 
> ```
> 
> such file  
> to load – testme (LoadError)  
> from ./testme:8
> 
> What’s wrong? Something with the rubygems installation?

(1) Double check that testme is truely installed in the  
/home/rrt/local/lib/site\_ruby/1.8.

(2) Make sure the file can be loaded correctly.

Try soemthing like this to see if it sheds any light:

load ‘/home/rrt/local/lib/site\_ruby/1.8/testme.rb’

– Jim W.

---

<div class="post-metadata">

**Author:** ![wybo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/cc9497/32.png) [@wybo](https://www.ruby-forum.com/u/wybo)\
**Post date:** [December 10, 2005, 11:04am UTC](https://www.ruby-forum.com/t/rubygems-in-require-no-such-file-to-load/49759/3 "2005-12-10T11:04:17Z")

</div>

On Fri, 9 Dec 2005, Jim W. wrote:

> > What’s wrong? Something with the rubygems installation?
> 
> (1) Double check that testme is truely installed in the  
> /home/rrt/local/lib/site\_ruby/1.8.
> 
> (2) Make sure the file can be loaded correctly.
> 
> Try soemthing like this to see if it sheds any light:
> 
> load ‘/home/rrt/local/lib/site\_ruby/1.8/testme.rb’

Thanks, Jim. This helped: we finally found out that the session gem  
wasn’t  
installed, but another session.rb was loaded instead.