rubycocoa-talk

[Rubycocoa-talk] Sob. Here I go again.

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

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 . . . .

Re: [Rubycocoa-talk] Sob. Here I go again.

[Tom C. <ta...@ca...>]

Have you tried the ruby packages from http://homepage.mac.com/discord/ 
Ruby/ ? I don't know whether they are sufficiently up-to-date now,  
but in my Panther days I found them very useful.

Tom


On 13 Sep 2005, at 09:56, Dave Howell wrote:

> 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 . . . .
>

Re: [Rubycocoa-talk] Sob. Here I go again.

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

On Sep 13, 2005, at 2:05, Tom Counsell wrote:

> Have you tried the ruby packages from 
> http://homepage.mac.com/discord/Ruby/ ? I don't know whether they are 
> sufficiently up-to-date now, but in my Panther days I found them very 
> useful.
I downloaded it, but since it apparently matters *which* 1.8.2 I 
install, and that site doesn't tell me what's actually in the package, 
I haven't tried it yet.

Re: [Rubycocoa-talk] Sob. Here I go again.

[Jonathan P. <jp...@dc...>]

On 13 Sep 2005, at 9:56, Dave Howell wrote:

> 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.

gcc-3.3 should work fine, or gcc-4.0 if you have Xcode 2.1.

Did you switch the link by hand? There's a tool to do this:  
gcc_select. Perhaps switching by hand broke things?

Look in the 'config.log' file to see what error messages the compiler/ 
linker spat out when failing. You could post the relevant excerpt  
here if it's not obvious.

> 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 . . . .

Probably won't work unless you copy all of /usr/local, due to library  
dependencies.

I use ruby from darwinports (www.darwinports.org) which installs  
into /opt/local. If there's some fundamental compiler problem on your  
system then it's unlikely to help though.

Re: [Rubycocoa-talk] Sob. Here I go again.

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

On Sep 13, 2005, at 2:22, Jonathan Paisley wrote:

> On 13 Sep 2005, at 9:56, Dave Howell wrote:
>
>> 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.
>
> gcc-3.3 should work fine, or gcc-4.0 if you have Xcode 2.1.

I don't. That's Tiger only.
> Did you switch the link by hand? There's a tool to do this: 
> gcc_select. Perhaps switching by hand broke things?

I did. Then I used gcc_select. Still didn't work.

> Look in the 'config.log' file to see what error messages the 
> compiler/linker spat out when failing. You could post the relevant 
> excerpt here if it's not obvious.

The error message in my original message was copied verbatim from the 
config.log. That's all it gave me.

Re: [Rubycocoa-talk] Sob. Here I go again.

[Jonathan P. <jp...@dc...>]

On 13 Sep 2005, at 10:36, Dave Howell wrote:

> The error message in my original message was copied verbatim from  
> the config.log. That's all it gave me.

There should be a bunch of stuff in the preceding lines, starting  
with an invocation of gcc that's intended to test that it's capable  
of building programs. If in doubt, post a page or two preceding the  
error message from config.log.

Re: [Rubycocoa-talk] Sob. Here I go again.

[Steven A. <st...@ne...>]

On Sep 13, 2005, at 4:56 AM, Dave Howell wrote:

> Fine. Download what ruby-lang.org tells me is the latest version.  
> Run ./configure.
> "configure:2045: error: C compiler cannot create executables" [...]
>
> My server, on which I'm trying to install Rails, has basically a  
> stock Apple install of 10.3.9.

Dumb question -- you _do_ have the latest xcode installed, and you  
_can_ compile other packages, right?

steve

Re: [Rubycocoa-talk] Sob. Here I go again.

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

  Jonathan Paisley wrote:
> Looks like your developer tools installation might have got broken at 
> some point. Can you try reinstalling the dev tools?

and Steven Arnold wrote:
> Dumb question -- you _do_ have the latest xcode installed, and you 
> _can_ compile other packages, right?

LOL. I don't think that's a dumb question at all. My /usr/bin directory 
has gcc-3.3 in it, but since so much Unix style installing is a "just 
type this line, everything will work fine, you don't need to know 
what's really going on", I have no idea what other dependencies are 
hidden beneath.

My general experience with installing anything from the command line 
has been horrible, (see 
http://howell.seattle.wa.us/essays/IHateUnix.html for one tragic 
example), so I try very hard not to compile anything, and haven't on 
the server in quite some time.

I believe I do not have 'the latest XCode' installed. My laptop has 
/Developer/Applications/Xcode (version 1.5). My server has 
/Developer/Applications/ProjectBuilder (2.0).

Guess I'll try installing XCode and see if that helps. . . . and 
eureka. Thank you both very much. Rails is now running. Haven't been 
able to get the postgres driver to install yet, but that appears to be 
a matter of psychically guessing what the answer is to the question 
"--with-pgsql-dir=" is.

Re: [Rubycocoa-talk] Sob. Here I go again.

[Jonathan P. <jp...@dc...>]

On 13 Sep 2005, at 22:25, Dave Howell wrote:

> I believe I do not have 'the latest XCode' installed. My laptop  
> has /Developer/Applications/Xcode (version 1.5). My server has / 
> Developer/Applications/ProjectBuilder (2.0).

ProjectBuilder, as far as I remember, is a pre-Xcode thing, so I  
guess that must be an old installation.

> Guess I'll try installing XCode and see if that helps. . . . and  
> eureka. Thank you both very much. Rails is now running. Haven't  
> been able to get the postgres driver to install yet, but that  
> appears to be a matter of psychically guessing what the answer is  
> to the question "--with-pgsql-dir=" is.

Hurrah!

The argument to --pgsql-dir is likely to be the 'prefix' directory  
into which postgres has been installed. The prefix directory is the  
one containing directories like 'bin', 'include', 'lib', 'sbin',  
'share'. For example, if you find your postgres programs in /usr/ 
local/bin, then probably --with-pgsql-dir=/usr/local may do the trick.

Re: [Rubycocoa-talk] Sob. Here I go again.

[Sam R. <sro...@un...>]

Quoting gr...@gr..., on Tue, Sep 13, 2005 at 02:25:56PM -0700:
> and Steven Arnold wrote:
> >Dumb question -- you _do_ have the latest xcode installed, and you 
> >_can_ compile other packages, right?
> 
> LOL. I don't think that's a dumb question at all. My /usr/bin directory 
> has gcc-3.3 in it, but since so much Unix style installing is a "just 
> type this line, everything will work fine, you don't need to know 
> what's really going on", I have no idea what other dependencies are 

And it usually works like that, on Unix. You're using OS X, its an odd
variant, with many strangenesses, for example, it doesn't actually come
with the development tools installed and automatically updated like the
rest of the s/w. Maybe one day Apple will see fit to use their s/w
updater for development tools...

I feel the pain of installing unix software on my OS X machine at home,
like you, and I develop full-time on Linux at work, so I'm pretty
familiar with "unix", but that doesn't always help. Eventually, enough
OS X users will submit patches to developers, and things will work
out-of-the-box more for them, but remember its still a fringe OS, from a
Unix point-of-view.

Cheers,
Sam