Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Dave H. <gr...@gr...>]

On Dec 8, 2005, at 0:36, Jonathan Paisley wrote:

> On 8 Dec 2005, at 1:50, Dave Howell wrote:
>
>> Go to web site. Go to download page. Download Panther installer. 
>> Install. Watch Ruby fail to compile.
>
> Please give precise details of the failure you experienced. What steps 
> did you take, and what results did you get? "fail to compile" isn't 
> enough information to help diagnose the problem.
>
> What version of OS X are you using? Have you done anything to the 
> standard Ruby installation (e.g., removed bits of it)?

As my earlier messages mentioned, I'm using Panther (as it happens, 
it's the current release, so it's 10.3.9), the error message is "can't 
open library: /usr/lib/libruby.1.dylib  (No such file or directory, 
errno = 2)", I'm using 1.8.2, which means I can't be using the 
"standard Ruby installation," and indeed, if I hadn't completely 
obliterated it from my OS (so, yes, I've removed bits. All the bits. 
Every last bit I could find), it would be happily compiling the *wrong* 
version of Ruby into my code and making my life incredibly miserable.

What steps did I take? I hit "Build and Run." For all of my current 
projects, even ones that have not changed at all since they last 
compiled successfully, I now get the same error message.

The question is: What did the pre-built Panther Install package screw 
up that the "ruby install.rb" script wasn't smart enough to fix? 
"libruby.1.dylib" is installed into /usr/local/lib. How do I force 
XCode to look where the library really is, and why didn't RubyCocoa's 
"install.rb" file set it up correctly in the first place? This was all 
working with RubyCocoa 0.4.1. Now it's not.

I could reset the files by restoring from my backups, but I rather 
doubt that the file containing the corrupted path is in the /usr tree, 
and I can't roll back my entire hard drive two days.