From: Dave H. <da...@gr...> - 2005-09-13 08:56:20
|
This is actually straight Ruby sadness, not specifically RubyCocoa. Anybody willing to suggest a place to get help if this isn't it, please do. Time to install Rails, I says to myself. Supposed to be a very simple three line process. Oops, but I have to have Gems 8.5 or later, and I have 8.3. OK, I'll ask 8.3 to update itself. Fails: it can't find an update path. Various attempts to get it to go in don't work. Eventually, I abandon Gems as incapable of handling its update, and download the package, unpack by hand, and run the installer from the command line. That appears to work. Dear Gem, install rails. Yes? Wonderful. ">rails /usr/local/bin/rails" Oh, but I'm not running 1.8.2. Except I am running 1.8.2, but it's apparently the November version, and Rails requires the December one. Fine. Download what ruby-lang.org tells me is the latest version. Run ./configure. "configure:2045: error: C compiler cannot create executables" I recall once before having to change from the default gcc3.3 compiler to something else. Sure enough, on my other system, gcc has been redefined as gcc-3.1. I switch the gcc link to 3.1. Doesn't work. I copy the gcc binary from my other computer to this one. Still doesn't work. My server, on which I'm trying to install Rails, has basically a stock Apple install of 10.3.9. Once again, just as I start to like Ruby, I get to descend to installer-failure hell. Sigh. I guess at this point, I could try obliterating /usr/local/bin/ruby entirely, and copy over the directory from my laptop. Yea, that sounds like a recipe for more not-working . . . . |