I ran into this issue when switching to ruby 1.9 and getting my paths mixed up.
Compare: ruby -ve 'p Gem.path' gem env (look for the GEM PATHS) If you gem env does have the path that ruby refs, create a symbolic link: ln -sf /path/to/gem/env/path /path/to/ruby/gem/path This worked for me, so hopefully with works for you. On Sat, Feb 27, 2010 at 3:48 PM, Kevin Baker <[email protected]> wrote: > ... after moving my app to a new server. All my gems are installed. If I > add new "require" statements for various packages, works fine. > > Is there something I am missing as far as environment? Hoping there is some > sort of "classpath" kind of issue. > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
