Note that there are some explanatory texts on larger screens.

plurals
  1. POpg gem '0.14.0' on Mountain Lion fails
    primarykey
    data
    text
    <p>I just upgraded from OS X Lion to OS X Mountain Lion. My rails environment for the most part stayed in tact.</p> <p>The only steps I had to do to get things back to a good state was: - Install XCode 4.4 - Install XCode 4.4 Command Line Tools - Install gcc-4.2</p> <p>So all that went well.</p> <p>Here's the issue, almost all my gems install properly when I run bundle install except for one of the most important ones I need - the postgresql gem 'pg'.</p> <p>And it specifically fails for versions above 0.12.2.</p> <p>I'm using ruby 1.9.3p125.</p> <p>I can successfully grab the 0.12.2 pg gem, and versions below, but they give me segmentation faults (I'm guessing because of the version of ruby I'm using).</p> <p>So this leads me to believe that it's specific to the pg gem, and not my overall environment seeing as other gems install fine.</p> <p>I also tried re-installing Postgresql to ensure my postgres environment is ok and seems good on that front.</p> <p>Has anybody been able to install the 'pg' gem version 0.13.0 or above (and more preferrably 0.14.X)?</p> <p>Here is my stack trace:</p> <pre><code>Building native extensions. This could take a while... ERROR: Error installing pg: ERROR: Failed to build gem native extension. /Users/caseyli/.rvm/rubies/ruby-1.9.3-p125/bin/ruby extconf.rb checking for pg_config... yes Using config values from /usr/bin/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 checking for PQisthreadsafe()... yes checking for PQprepare()... yes checking for PQexecParams()... yes checking for PQescapeString()... yes checking for PQescapeStringConn()... yes checking for PQescapeLiteral()... yes checking for PQescapeIdentifier()... yes checking for PQgetCancel()... yes checking for lo_create()... yes checking for pg_encoding_to_char()... yes checking for pg_char_to_encoding()... yes checking for PQsetClientEncoding()... yes checking for PQlibVersion()... yes checking for PQping()... yes checking for rb_encdb_alias()... yes checking for rb_enc_alias()... no checking for PGRES_COPY_BOTH in libpq-fe.h... no checking for struct pgNotify.extra in libpq-fe.h... yes checking for unistd.h... yes checking for ruby/st.h... yes creating extconf.h creating Makefile make compiling pg.c pg.c: In function ‘pg_s_library_version’: pg.c:273: warning: implicit declaration of function ‘PQlibVersion’ pg.c: In function ‘Init_pg_ext’: pg.c:384: error: ‘PQPING_OK’ undeclared (first use in this function) pg.c:384: error: (Each undeclared identifier is reported only once pg.c:384: error: for each function it appears in.) pg.c:386: error: ‘PQPING_REJECT’ undeclared (first use in this function) pg.c:388: error: ‘PQPING_NO_RESPONSE’ undeclared (first use in this function) pg.c:390: error: ‘PQPING_NO_ATTEMPT’ undeclared (first use in this function) make: *** [pg.o] Error 1 Gem files will remain installed in /Users/caseyli/.rvm/gems/ruby-1.9.3- p125@elliottfarmequipment/gems/pg-0.14.0 for inspection. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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