[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Ruby Installation Mac Leopard

Michael Rigart

12/24/2008 9:54:00 AM

Hi everybody

I don't know if I post this in the right forum but I would like to
install a Ruby on Mac OSX Leopard. I know it comes stock with Leopard,
but with the dificulties there has been with Rails 2.2 and MySQL on
Leopard, it seems to be that the best way to go is just to get a new
install of Ruby.

The main problem is that MySQL is installed as 64bit and the stock Ruby
interpreter as 32 bit. I have seen solutions that say installing 32bit
of MySQL solves the problem, but I don't want to downgrade. I have a
64bit machine, so god forbid me I want to use it the way it was
intended.

My concern however is that I don't want to break the current stock
installation because it hangs together with RubyCocoa and consorts. But
I wan't to be able to use my new Ruby installation in a fashionable way:
using the ruby command by just typing "ruby", etc.

I was also wondering if I could use the stock RubyGems and others with
the new Ruby installation.

I have found: http://danbenjamin.com/articles/2008/02/ruby-rai...
instructions, but I still a bit unsure what to do. If just installing
ruby would do the trick, or if I really need to reinstall RubyGems. This
is my first month walking the Mac path and I don't want to break stuff
making my laptop completely useless and getting frustrated to fix it
again.

I know I could install MacPorts, but I hate having software installed
twice on a system and I would like to keep everything as stock as
possible.

thank you in advance for the support and happy holidays to you all.
--
Posted via http://www.ruby-....
2 Answers

David Rio

12/24/2008 10:18:00 AM

0

On Wed 24.Dec'08 at 18:54:07 +0900, Michael Rigart wrote:
> I don't know if I post this in the right forum but I would like to
> install a Ruby on Mac OSX Leopard. I know it comes stock with Leopard,
> but with the dificulties there has been with Rails 2.2 and MySQL on
> Leopard, it seems to be that the best way to go is just to get a new
> install of Ruby.
>
> The main problem is that MySQL is installed as 64bit and the stock Ruby
> interpreter as 32 bit. I have seen solutions that say installing 32bit
> of MySQL solves the problem, but I don't want to downgrade. I have a
> 64bit machine, so god forbid me I want to use it the way it was
> intended.
>
> My concern however is that I don't want to break the current stock
> installation because it hangs together with RubyCocoa and consorts. But
> I wan't to be able to use my new Ruby installation in a fashionable way:
> using the ruby command by just typing "ruby", etc.
>
> I was also wondering if I could use the stock RubyGems and others with
> the new Ruby installation.
>
> I have found: http://danbenjamin.com/articles/2008/02/ruby-rai...
> instructions, but I still a bit unsure what to do. If just installing
> ruby would do the trick, or if I really need to reinstall RubyGems. This
> is my first month walking the Mac path and I don't want to break stuff
> making my laptop completely useless and getting frustrated to fix it
> again.
>
> I know I could install MacPorts, but I hate having software installed
> twice on a system and I would like to keep everything as stock as
> possible.

Hi Michael,

I would recommend you to install those bits in your home directory. The
process would look something like:

1. Download ruby sources or checkout the svn repository. Compile and
install in $HOME/local.

2. Change your $PATH to ensure your shell finds the ruby you just
installed.

3. Install rubygems

4. Install whatever gems you want...

5. Install mysql in your $HOME/local. That's a little bit trickier but there
are many howtos/tutorials out there. This is pretty good:

http://www.washington.edu/computing/web/publishing/mysql-in...

You are now good to go. If you want to run any ruby code with the preinstalled
version of ruby just use the full fs path (/usr/bin/ruby ...).

-drd

Michael Rigart

12/25/2008 1:14:00 PM

0

Thanks for the info, but I found another solution. I just recompiled the
stock MySQL as a Universal build. All other blog posts mentioned running
2 mysql instances, but why no recompiling the stock one as a universal
build is still a question for me. Now I have i386 and x86_64 support :)
and everything seems to work.
--
Posted via http://www.ruby-....