This smells like a borked Ruby installation, or multiple Ruby
installations conflicting with each other, or something like that.
Have you installed Ruby multiple times? How did you install the Ruby
you're using in /opt/local/bin? MacPorts, I'm guessing?
Chris
The Ruby that comes with Leopard is perfectly adequate (it's what I'm
using for development), unless you specifically want a newer version.
Some people like to install through Ports or Fink or build it themselves
regardless, but I think that's just a waste of time and disk space.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
--
Posted via http://www.ruby-forum.com/.
Can't say I've run into that. Info?
(For the record, the only projects on which I've been using BigDecimal
at all have been using Rubinius or JRuby, not MRI.)
>
> Fred
Ouch! I think I'm using patchlevel 287, which would imply that a later
upgrade to Snow Leopard fixed the patch, but I'm not at that computer
right now to check. If I *am* using the faulty version, that implies
that I finally have a use for RVM.
> Nat
Well, there's nothing fundamentally wrong with having multiple Rubies
on one system. Before RVM [1] came along, I always used to compile my
own Ruby into /usr/local, and it seemed to live perfectly happy
alongside OS X's built-in Ruby.
So, the fact that MacPorts' Ruby is misbehaving in this way on your
system is strange. But unless you're particularly interested in
fathoming that problem out, the quickest fix (as Marnen and Nat have
suggested) would be to uninstall MacPorts' Ruby and use OS X's
instead, or use RVM to install your Rubies.
Chris