StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POrvm upgrade fails - OSX Lion
text
Body
copied!<blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/14072524/error-installing-ruby-with-rvm-osx-10-8">Error installing Ruby with RVM (OSX 10.8)</a> </p> </blockquote> <p>I'm trying to upgrade my Ruby version - right now I'm on p194 - and I saw that there's p362 available. Note: I'm new at this, sorry if I'm misunderstanding something.</p> <p>I'm on Macbook Pro, OSX 10.7.5, and my ruby versions is:<br /></p> <pre>[~]$ruby -v ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0]</pre> <p>So when I try to upgrade using RVM, I run this command:<br /></p> <pre>[~]$rvm upgrade 1.9.3-p194 1.9.3-p362</pre> <p>And then it asks me for confirmation, I say Yes, and it runs, and then it gives me error:<br/></p> <pre>Installing new ruby ruby-1.9.3-p362 No binary rubies available for: downloads/ruby-1.9.3-p362.<br /> Continuing with compilation. Please read 'rvm mount' to get more information on binary rubies.<br /> Installing Ruby from source to: /usr/local/rvm/rubies/ruby-1.9.3-p362, this may take a while depending on your cpu(s)...<br /> ruby-1.9.3-p362 - #downloading ruby-1.9.3-p362, this may take a while depending on your connection...<br /> ruby-1.9.3-p362 - #extracted to /usr/local/rvm/src/ruby-1.9.3-p362 (already extracted)<br /> Patch segfault_fix_7629 was already applied.<br /> ruby-1.9.3-p362 - #configuring<br /> Error running 'env LDFLAGS=-L/opt/sm/pkg/active/lib CFLAGS=-I/opt/sm/pkg/active/include CPATH=/opt/sm/pkg/active/include ./configure --enable-shared --disable-install-doc --prefix=/usr/local/rvm/rubies/ruby-1.9.3-p362 --with-opt-dir=/usr/local/rvm/usr', please read /usr/local/rvm/log/ruby-1.9.3-p362/configure.log<br /> There has been an error while running configure. Halting the installation.<br /> Migrating gems from 1.9.3-p194 to ruby-1.9.3-p362<br /> Ruby 'ruby-1.9.3-p362' is not installed - please install it first.<br /> Error migrating gems.<br /></pre> <p>So then I run:<br /></p> <pre>[~]$rvm install ruby-1.9.3-p362</pre> <p>and I get this for error:<br /></p> <pre>No binary rubies available for: downloads/ruby-1.9.3-p362. Continuing with compilation. Please read 'rvm mount' to get more information on binary rubies. Installing Ruby from source to: /usr/local/rvm/rubies/ruby-1.9.3-p362, this may take a while depending on your cpu(s)... ruby-1.9.3-p362 - #downloading ruby-1.9.3-p362, this may take a while depending on your connection... ruby-1.9.3-p362 - #extracted to /usr/local/rvm/src/ruby-1.9.3-p362 (already extracted) Patch segfault_fix_7629 was already applied. ruby-1.9.3-p362 - #configuring Error running 'env LDFLAGS=-L/opt/sm/pkg/active/lib CFLAGS=-I/opt/sm/pkg/active/include CPATH=/opt/sm/pkg/active/include ./configure --enable-shared --disable-install-doc --prefix=/usr/local/rvm/rubies/ruby-1.9.3-p362 --with-opt-dir=/usr/local/rvm/usr', please read /usr/local/rvm/log/ruby-1.9.3-p362/configure.log There has been an error while running configure. Halting the installation.</pre> <p>So then I went to open up that log file that it's referencing to, and here are the contents:<br /></p> <pre>[2013-01-15 23:01:13] env LDFLAGS=-L/opt/sm/pkg/active/lib CFLAGS=-I/opt/sm/pkg/active/include CPATH=/opt/sm/pkg/active/include ./configure --enable-shared --disable-install-doc --prefix=/usr/local/rvm/rubies/ruby-1.9.3-p362 --with-opt-dir=/usr/local/rvm/usr checking build system type... x86_64-apple-darwin11.4.2 checking host system type... x86_64-apple-darwin11.4.2 checking target system type... x86_64-apple-darwin11.4.2 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.</pre> <p>Please advise on what's happening here and how to correct this issue.</p> <p>Thank you in advance.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload