StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I just went to install rvm for the first time, which worked. It spits out a warning about ruby 1.9.2, so i built and installed 1.9.3, using (I am on 10.7.2, with Xcode 4.2)</p> <pre><code>rvm install 1.9.3 && rvm use 1.9.3 --default </code></pre> <p>Worked fine. But heroku does not have support in cedar for 1.9.3 yet (or at least they don't claim it), so i really wanted to run 1.9.2. So i tried:</p> <pre><code>rvm install 1.9.2 && rvm use 1.9.2 --default </code></pre> <p>And it also worked... So I am not sure what happened 'right' here. I have Xcode 4.2 installed in the default location, but I also have Xcode 4.1 installed in 'Developer4.1'. I installed 4.2 after I renamed my 4.1 install. Hope this helps someone.</p> <pre><code> ruby-1.9.2-p290 - #extracting ruby-1.9.2-p290 to /Users/tandersen/.rvm/src/ruby-1.9.2-p290 ruby-1.9.2-p290 - #extracted to /Users/tandersen/.rvm/src/ruby-1.9.2-p290 Fetching yaml-0.1.4.tar.gz to /Users/tandersen/.rvm/archives Extracting yaml-0.1.4.tar.gz to /Users/tandersen/.rvm/src Configuring yaml in /Users/tandersen/.rvm/src/yaml-0.1.4. Compiling yaml in /Users/tandersen/.rvm/src/yaml-0.1.4. Installing yaml to /Users/tandersen/.rvm/usr ruby-1.9.2-p290 - #configuring ruby-1.9.2-p290 - #compiling ruby-1.9.2-p290 - #installing Removing old Rubygems files... Installing rubygems-1.8.10 for ruby-1.9.2-p290 ... Installation of rubygems completed successfully. ruby-1.9.2-p290 - adjusting #shebangs for (gem irb erb ri rdoc testrb rake). ruby-1.9.2-p290 - #importing default gemsets (/Users/tandersen/.rvm/gemsets/) Install of ruby-1.9.2-p290 - #complete Using /Users/tandersen/.rvm/gems/ruby-1.9.2-p290 Snow-Pro:~ tandersen$ Snow-Pro:~ tandersen$ irb ruby-1.9.2-p290 :001 > x = 3 => 3 ruby-1.9.2-p290 :002 > x*x => 9 </code></pre>

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