@rebecca : I didn't find any SO offerings on the issues either. It was a painful day+ for me too. I'm glad at least you were able to reach out. @ian : I _was_ using RVM... it's a moot point. @bill : Interesting... haven't tried that yet. How would RailsApps have prevented the ElCapitan linking problem?
On Mon, Feb 8, 2016 at 7:53 PM Bill Vieux <[email protected]> wrote: > I can't recommend RailsApps and Daniel Kehoe strongly enough. > > http://railsapps.github.io/installrubyonrails-mac.html > > Saved me hours if not days of pain. > > > On Monday, February 8, 2016, Rebecca Colavin <[email protected]> wrote: > >> Thanks Ian. >> >> I have a good basic understanding of getting an app up and running >> (thanks LEARN academy!) so learning to use the tools you mention is the >> sensible next step. >> >> Best, >> >> Rebecca >> >> >> On Monday, February 8, 2016 at 5:31:12 PM UTC-8, Ian Young wrote: >>> >>> Hey Rebecca, >>> >>> I think the lesson here is "use rbenv or rvm". These tools let you >>> control your version of Ruby and upgrade on your own time rather than when >>> your OS decides to. And just as importantly, they give you a Ruby that's a >>> known quantity rather than whatever random changeset the OS developers >>> grabbed and patched with who-knows-what and compiled with whatever flags >>> they felt like using. If every Rubyist was using these tools, we'd see a >>> vast reduction in overall grief. >>> >>> However, I am conflicted about offering that advice to someone who's >>> starting with Ruby for the very first time. The process of getting your >>> first Rails app from zero to booted is already pretty long and filled with >>> installing and configuring mysterious things ("Ok, I downloaded Xcode, now >>> I need homebrew, I guess? Wait, why am I installing Node.js? What's a >>> coffee script?"), and rbenv/rvm adds one more mysterious tool to configure, >>> not to mention one more decision that the newbie is not equipped to make. I >>> wish there were a way to catch people right before they encounter their >>> first major Ruby headache and funnel them to rbenv/rvm just in time. >>> >>> Ian >>> >>> >>> On Mon, Feb 8, 2016, at 04:15 PM, Rebecca Colavin wrote: >>> >>> Hi Peter. >>> >>> There's a lesson here somewhere.... it may be "if you had installed El >>> Capitan in a timely manner you would have heard about this when we were all >>> talking about it" or "searching StackOverFlow requires some level of >>> understanding" or possibly "By Grabthar's hammer, by the suns of Worvan, >>> you shall be avenged." >>> >>> It's always so simple once you know the answer. >>> >>> Thanks for the support, >>> >>> Rebecca >>> >>> On Monday, February 8, 2016 at 3:57:39 PM UTC-8, Peter Fitzgibbons wrote: >>> >>> You updated Ruby. The update to El Capitan breaks some of the dynamic >>> links that were compiled into ruby. >>> The El cap upgrade also btw breaks many homebrew installs. I >>> personally had to uninstall/reinstall many of the homebrew apps (postgres, >>> redis, etc) >>> Thanks for posting your findings! >>> >>> On Mon, Feb 8, 2016 at 3:49 PM Rebecca Colavin <[email protected]> wrote: >>> >>> Howdy All >>> >>> This was supposed to be a post begging for help... I have been having a >>> segmentation fault when running "rails generate rspec:install" on a Mac. No >>> posts on StackOverflow (stop spring etc) were any help whatsoever. Just >>> before submitting to the group, I updated from OSX from Yosemite to El >>> Cap, uninstalled and reinstalled rails, postgresql (I had previously had >>> issues with installing the pg gem) and rspec. I updated ruby (2.0.0 to >>> 2.0.0p643). >>> >>> Note that I had previously tried reinstalling rails with no effect >>> whatsoever on the problem. >>> >>> I had previously been able to use rspec without incident. I do not know >>> which particular dependency caused the problem but I just wanted to post >>> here so the issue (and lame-brain solution) is documented. If someone has >>> an idea what might have been the actual problem, that might be useful! I >>> have the diagnostic report, if you should a need for a headache (I >>> certainly have one). >>> >>> I hope my experience may be of help to some other poor newbie. >>> >>> Thank you, >>> >>> Rebecca >>> >>> >>> >>> >>> >>> -- >>> -- >>> SD Ruby mailing list >>> [email protected] >>> http://groups.google.com/group/sdruby >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "SD Ruby" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> -- >>> SD Ruby mailing list >>> [email protected] >>> http://groups.google.com/group/sdruby >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "SD Ruby" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >> -- >> -- >> SD Ruby mailing list >> [email protected] >> http://groups.google.com/group/sdruby >> --- >> You received this message because you are subscribed to the Google Groups >> "SD Ruby" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
