[MacPorts] #31756: ruby19 @1.9.2-p290

[MacPorts]

#31756: ruby19 @1.9.2-p290
------------------------------------+---------------------------------------
 Reporter:  joshuajmoody@…          |       Owner:  kimuraw@…           
     Type:  defect                  |      Status:  new                 
 Priority:  Normal                  |   Milestone:                      
Component:  ports                   |     Version:  2.0.3               
 Keywords:  lion                    |        Port:  ruby19              
------------------------------------+---------------------------------------

Comment(by joshuajmoody@…):

 > The comment says "ruby-1.9.x built with clang or llvm-gcc does not
 work", and you only said you were able to build it. Were you actually able
 to run it also?

 I am able to run ruby19.  I installed rb19-rails and was able to stand up
 a demo rails site on my machine.

 > Also, it might help to diagnose your earlier build failure if you attach
 the config.log.

 I did a clean install of MacPorts 2.0.3 in an alternative location.  I
 have attached a config.log and a main.log for a failed ruby19 build.  I
 have also attached the main.log for the successful ruby19 build (halted
 during the port staging phasing)

 > It looks like MacPorts selected the "Mac OS X gcc 4.2", which I would
 not have expected, given that you have Xcode 4.2, which does not include
 any version of gcc.

 This machine has previously had Xcode 3.*, Xcode 4.0, and Xcode 4.1
 installed on it.  For a time it had both Xcode 4.1 and 4.2 installed.

 Here is some information about gcc-4.2 on my machine:

 {{{
 moody% ls -al `which gcc-4.2`
 -rwxr-xr-x  1 root  wheel  113024 May 16 05:37 /usr/bin/gcc-4.2
 moody% gcc-4.2
 gcc-4.2: error trying to exec '/usr/bin/i686-apple-darwin11-gcc-4.2.1':
 execvp: No such file or directory
 }}}

 Do you require other information?

 Thanks for looking into this.

-- 
Ticket URL: <https://trac.macports.org/ticket/31756#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS