![]() To install OS X Mavericks from scratch, you will first need to create an installation USB that you will use to boot your Mac from. Needless to say, you should have a backup of all your important data somewhere outside your Mac. If you are one of those Mac users, here is a simple guide to perform a clean install of OS X Mavericks. But you should really get to know and love MacPorts, it is your friend.However, some users actually prefer to do a clean install on these occasions due to the advantages that such procedures bring, like getting rid of system errors and unnecessary files that might get carried over to the new OS if we simply update it for example. MacPorts won't affect OS X version of anything, nor homebrew (except to make it superfluous) and keeps everything it installs in /opt making deinstallation a breeze (but this has nothing to do with where ruby keeps its gems, ~/.gem ). If there's trouble try sudo port upgrade outdated Take a look at what MacPorts has for ruby port search ruby |lessĪnd/or just install nokogiri sudo port -vsk install ruby19 libxml2 libxslt Install MacPorts curl -Ok Īdd MacPorts to your $PATH: export PATH=/opt/local/bin:/opt/local/sbin:$PATH That's what's nice about MacPorts (and any mature package manager) it takes care of the dependecies for you if they're not installed. It appears from your provided logs that you're missing stuff. rvm uses MacPorts by default if it is installed. MacPorts requires an appropriate version of xcode xcode_5.1.1.dmg is the most recent version for Mavericks. all my installations, but also the various versions of ruby installations that are necessary to use the gems I want. Not me.īrewinistas enthusiasm notwithstanding, the homebrew package manager has growing pains typical of an immature package management solution. IMO, ruby is broken, someone's going to have to pull it out and get it neatly reeled in for it to be fixed, and I'm just not up to it. ruby is really starting to chafe, because while the support information might be out there, it is looking more and more like a fishing reel that has birdnested. Ruby was once quite easy to use, but now, the number of versions that necessarily need to be supported are legion, and gem developers sometimes force you to install a new version of ruby at some other version when you already have a perfectly good ruby installation! Grr. But you can install multiple versions of ruby, and you'll definately need a ruby version manager if you intend to use lots of gems. Most rubiers will tell you don't even bother useing the ruby that ships with OS X. Do not try to remove the version of ruby that ships with OS X or update or upgrade it unless with App Store/Software Update/softwareupdate. You can't assume that the version of ruby built-into OS X is compatible with any gems you want to use. I'd really like to get back to actually developing. ![]() I've wasted at least a day on this - just trying to get one Ruby gem installed. I've tried installing nokogiri by passing paths to libxml2, libxslt, and libiconv in /usr/local/Cellar/, but the install still fails, with same errors as above. I've also brew install apple-gcc42 and linked, as per how tos I've found. I've tried installing all of these without the ARCHFLAG in. I have libxml2, libxslt, and libiconv installed via Homebrew, and each is linked. My ~/.bash_profile has 64bit compiling forced by: export ARCHFLAGS="-arch x86_64" I have xcode and it's command tools installed. Ld: warning: ignoring file /usr/local/Cellar/libiconv/1.14/lib/libiconv.dylib, **file was built for x86_64 which is not the architecture being linked (i386)**: /usr/local/Cellar/libiconv/1.14/lib/libiconv.dylib Ld: warning: ignoring file /usr/local/Cellar/libxml2/2.9.1/lib/libxml2.dylib, **file was built for x86_64 which is not the architecture being linked (i386)**: /usr/local/Cellar/libxml2/2.9.1/lib/libxml2.dylib However, looking at nokogiri's mkmf.log, the following errors are shown: ld: warning: ignoring file /usr/local/Cellar/libxslt/1.1.28/lib/libxslt.dylib, **file was built for x86_64 which is not the architecture being linked (i386)**: /usr/local/Cellar/libxslt/1.1.28/lib/libxslt.dylib noĬhecking for libiconv_open() in -liconv. noĬhecking for libiconv_open() in iconv.h. Install fails showing: checking for iconv_open() in iconv.h.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |