osx-mavericks

I'm attempting to run bundle in my Rails project on OSX 10.9. It fails when getting to the pg gem with this error: Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /Users/kyledecot/.rvm/rubies/ruby-2.0.0-p247/bin/ruby extconf.rb checking for pg_config... no No pg_config... trying anyway. If building fails, please try again with --with-pg-config=/path/to/pg_config checking for libpq-fe.h... yes checking for libpq/libpq-fs.h... yes checking for pg_config_manual.h... yes checking for PQconnectdb() in -lpq... yes checking for PQconnectionUsedPassword()... yes

Python interpreter is crashing when I run the second command. I have searched the web for this error and did not found anything. The error is showed below: Python 2.7.5 (v2.7.5:ab05e7dd2788, May 13 2013, 13:18:45) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> print 1 1 >>> print 2 Segmentation fault: 11 Why? I'm using Mac OS X Mavericks. I think that's relevant since it's a beta version. EDIT: Forgot the problem details provided by the OSX: Process: Python [11053] Path: /Library/Frameworks/Python.framework

I've just updated my Mac OS to 10.9 and I discovered that some (all?) of my Python modules are not here anymore, especially the Image one. So I try to execute sudo pip install pil , but I get this error: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/tk.h:78:11: fatal error: 'X11/Xlib.h' file not found # include <X11/Xlib.h> ^ 1 error generated. error: command 'cc' failed with exit status 1 My Xcode is up-to-date and I don't have any idea. Is it possible that PIL is not yet 10.9 compatible ? Following worked for me: ln -s

I just noticed that after installing OS X 10.9, the g++ compiler links to the clang compiler. Is there anyway to revert back to gcc/g++? It has been this way for a long time already. The "GCC" that came with 10.8 was really GCC front-end with LLVM back-end. The best way to get GCC is via Homebrew . After the one-line homebrew install command on the bottom of the linked page, you just need: $ brew install gcc49 Unlike macports, Homebrew doesn't clutter your system dirs and it's much better at managing versions and uninstalls. It also doesn't require the crutch known as sudo . You'd have to