Comments on: warning: already initialized constant OPTIONS

By: Natalie

Natalie — Wed, 30 Jul 2008 20:15:31 +0000

Apparently it also happens if you accidentally have a circular include. The weird thing is I thought there was a different error message for circular requires, but I wasn’t getting it, just the “warning: already initialized constant” thing. But when I tracked down and removed the circular require it fixed it.

By: muni

muni — Mon, 04 Feb 2008 14:17:47 +0000

Hai,

i am new to Rails, i am struggling with the same above problem .so can any body give me detailed explanation how to solve this problem. i didnt understand what u r saying, so any body help me please. almost it sucks 2 days..

Thanks,
Muni.

By: Jacob

Jacob — Wed, 05 Dec 2007 16:08:50 +0000

That’s not the only error that can crop up from requiring a non-existant file.

It seems like a bug to me, What should really happen is a MissingSourceFile exception, which I actually see if I downgrade to rails 1.1.6

here are some other strange exceptions/behavior I’ve seen, all caused by requiring a missing file or gem:
http://dev.rubyonrails.org/ticket/10376

By: Alex

Alex — Sat, 01 Dec 2007 20:38:59 +0000

hey thanks for the post and the comments. this error message sucks, indeed.

By: JoNtE

JoNtE — Wed, 14 Nov 2007 13:17:44 +0000

Had the same problem.
A tip is to start webrick instead.

At least it will tell you which gem that it fails to load ;)

ruby script/server webrick
Like:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require’: no such file to load — GD (MissingSourceFile)

By: Sean Schofield

Sean Schofield — Thu, 27 Sep 2007 12:26:10 +0000

What a horribly vague error message. I fixed the problem as well. I had done a little “tidying” of my code and accidentally removed my own library that I was “requiring.” It would be nice if we could be told the name of the missing resource (or at least that there was a missing resource.)

By: antono

antono — Wed, 15 Aug 2007 11:46:05 +0000

Thanks! It helps me :)
I’ve missed rmagic on my Debian box.

aptitude install librmagick-ruby

By: Leevi Graham

Leevi Graham — Sat, 04 Aug 2007 02:32:18 +0000

OK sorted this one out.

The solution for me was installing the ruby-debug gem – sudo gem install ruby-debug

The reason: /config/environments/development.rb requires it.

begin
require ‘ruby-debug’
rescue
config.breakpoint_server = true
end

By: Dan

Dan — Wed, 18 Jul 2007 04:09:46 +0000

Apparently, this happens if you require any non-existing file from within config/environment.rb

After switching my rails app to another server, I was getting that cryptic error message when I ran script/server. Turns out I had a “require ‘json’” in environment.rb, but didn’t have the json gem installed.

It’s not necessarily related to missing gems, it can be easily reproduced if you “require ‘nonexistingfile’”.

By: dansketcher

dansketcher — Tue, 05 Jun 2007 07:54:01 +0000

There were heaps: log4r, calibre, sentry… I’m not sure which one it was exactly, but it was definitely a missing dependency issue