Robert Mannl said:
> Yeah, there are the three dirs/files you said:
>
> /usr/lib/ruby/gems/1.8/gems/rmagick-1.8.1
> /usr/lib/ruby/gems/1.8/specifications/rmagick-1.8.1.gemspec
> /usr/lib/ruby/gems/1.8/gems/rmagick-1.8.1/gem_make.out

Interesting.  All the pieces are there for RubyGems to find the RMagick
file.  What does running 'gemwhich RMagick' at the command line report.

I suppose it is possible that the RMagick ruby file can't load the C
library (for some reason) and is aborting (silently??) without defining
the RMagick module.

Try this Ruby script.  It tries to load your rmagick file without going
through RubyGems.  If it works, then the problem is probably gem runtime
related.  If it doesn't work, then the problem is probably installation
issues, either with the gem or with rmagic.

   $: << '/usr/lib/ruby/gems/1.8/gems/rmagick-1.8.1/lib'
   require 'RMagick'

> I also checked the config.log (I read about that file somewhere on the
> web), to see how it was installed/compiled.
>
> Here it is: http://rafb.net/paste/results/K8ipJ244.html
>
> There are several "undefined references" there, e.g.:
> "undefined reference to `ParseSizeGeometry'"
>
> I don't know if that means anything.

Ack ... I don't know enough about RMagick to interpret this file.

-- 
-- Jim Weirich     jim / weirichhouse.org    http://onestepback.org
-----------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct,
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)