Phillip Gawlowski
12/14/2008 1:45:00 AM
Tom Cloyd wrote:
>> If I'm going to use my new Ruby 1.8.7 and want it to use the latest
>> rubygems, which I presume IS somewhere in my filesystem, what do I
>> need to do? Anything at all?
You'll need to compile it without suffix (how escapes me right now, I'm
afraid, but it is probably ./configure --no-suffix or something like
that), and issue "make install" after you are done. However, the easiest
way is possibly to apt-get install ruby1.8, and change any symlinks to
ruby1.8, instead of ruby1.9, so that the ruby command is actually
ruby1.8 (clear as mud?)
And Ruby 1.9 could be used by Amarok, or Kubuntu's own scripts. However,
multiple versions can co-exist somewhat happily (Depends on how the
scripts by the 3rd party are written. If you are unlucky, they simply
assume that /bin/ruby == /bin/ruby1.9 and could break).
> An update - thought I'd try to install a gem, just to see the response.
> It wasn't good, and I don't know what it means...
>
> $ sudo gem install RedCloth
> [sudo] password for tomc:
> Building native extensions. This could take a while...
> ERROR: Error installing RedCloth:
> ERROR: Failed to build gem native extension.
>
> /usr/bin/ruby1.9 extconf.rb install RedCloth
> extconf.rb:1:in `require': no such file to load -- mkmf (LoadError)
> from extconf.rb:1:in `<main>'
>
>
> Gem files will remain installed in
> /var/lib/gems/1.9.0/gems/RedCloth-4.1.1 for inspection.
> Results logged to
> /var/lib/gems/1.9.0/gems/RedCloth-4.1.1/ext/redcloth_scan/gem_make.out
> tomc@tomc-desktop:~$
>
> I send this along simply thinking it may give additional useful
> information.
Sorta. For one, it shows that Ruby 1.8 was *not* installed. At least not
properly. Do you have a ruby1.8 executable?
Also, you'll have to install the build-essentials package to get a
compiler toolchain.
Cheers,
-P
P.S.: I'm not using Linux anymore, so take my help with a grain of salt.