On 2009/02/16, at 23:16, Christian Bryan wrote:
Mm, uh oh.
What do you get when you do a `which ruby`? I have the funny feeling
that macports is trying to build shoes against the default osx
version of ruby and not the macports version.
You were right. Although I have re-installed OS X in my macbook, I was
using the default osx ruby (which I still do). But that shouldn't be a
problem for your portfile. I can have both of them at the same time,
like I do with several python tools that are macports specific.
To correct the problem, I believe referencing ruby by the full path
(inside Macport's path) should do the trick.
Alcides Fonseca
