Comments on: Livin’ on the edge: Ruby, Rails, and Snow Leopard

By: Suzi Holihan

Suzi Holihan — Thu, 09 Sep 2010 19:01:15 +0000

Naja denke ich die Power Neujahrsnacht still und klar, deutet auf ein gutes Jahr!

By: AndyL

AndyL — Sun, 04 Oct 2009 16:07:09 +0000

So, instead of “rvm use ruby -v 1.9.1″, the new instructions are:

$ rvm install 1.9.1

Then:
$ rvm 1.9.1
…to use it.

Please update your post if you can. Thanks.

By: AndyL

AndyL — Sun, 04 Oct 2009 15:58:07 +0000

Solved it. Installing now with:
rvm install 1.9.1

By: AndyL

AndyL — Sun, 04 Oct 2009 15:53:45 +0000

I get this error:
→ rvm use ruby -v 1.9.1
Ruby implementation ” is not known.
no default rvm specified, defaulting to pre-rvm sytem.

What could be going on?

By: Kristen

Kristen — Wed, 30 Sep 2009 07:23:25 +0000

Im getting the “Forbidden. You don’t have permission to access / on this server.” error when I navigate to my rails app in the browser. Its working with script/server, so I think its Passenger…Can someone help please?

By: Peter Marks

Peter Marks — Sun, 20 Sep 2009 17:58:09 +0000

I finally got this up and running. Despite installing xcode, I was still left with 32-bit ruby 1.8.6 in usr/local. Building 1.8.7 resolved all of my architectural incompatibility issues.

By: MikkelFJ

MikkelFJ — Tue, 15 Sep 2009 22:11:30 +0000

try
sudo port clean gawk
sudo port uninstall gawk
sudo port install gawk
sudo port upgrade outdated

it seems gawk is expecting a 32 bit version of libintl, but it is a 64 bit version. After doing the above I got past the libintl problem. Selfupdate was not sufficient.
This was on leopard to snow, from tiger to snow I did not have this problem, but others …

By: Rails finally working with Snow Leopard

Rails finally working with Snow Leopard — Tue, 15 Sep 2009 21:10:14 +0000

[...] thanks for TWG for their support on the matter. They did point out the problem as a bug in MacPort but I thought [...]

By: Bashar

Bashar — Tue, 15 Sep 2009 20:35:18 +0000

Hey guys… just to update on what happened to me. I just left it for sometime and got busy with other stuff, and it would seem really to be a bug with MacPort as today I tried to do sudo port selfupdate again, and after that sudo port upgrade worked just fine.

I have other errors now. I’ll chase’em up :)
Thanks

By: Georges

Georges — Thu, 10 Sep 2009 19:29:01 +0000

This kind of a shot in the dark, but do you guys have the most recent MacPorts installed?

Try: sudo port selfupdate

1.8.0 has worked perfectly for me, but I installed everything from scratch.