1

I am trying to bundle install my Gemfile at Yosemite, I have pg listed, but I get this error:

Installing pg 0.18.1 with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    /Users/Apple/.rvm/rubies/ruby-2.2.2/bin/ruby -r ./siteconf20150811-78520-18pzkkt.rb extconf.rb
checking for pg_config... yes
Using config values from /usr/local/php5/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 PQsetSingleRowMode()... yes
checking for PQconninfo()... yes
checking for PQhostaddr()... no
checking for rb_encdb_alias()... yes
checking for rb_enc_alias()... yes
checking for rb_thread_call_without_gvl()... yes
checking for rb_thread_call_with_gvl()... yes
checking for rb_thread_fd_select()... yes
checking for rb_w32_wrap_io_handle()... no
checking for rb_str_modify_expand()... yes
checking for rb_hash_dup()... yes
checking for PGRES_COPY_BOTH in libpq-fe.h... yes
checking for PGRES_SINGLE_TUPLE in libpq-fe.h... yes
checking for PG_DIAG_TABLE_NAME in libpq-fe.h... yes
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 "DESTDIR=" clean

make "DESTDIR="
compiling gvl_wrappers.c
compiling pg.c
compiling pg_binary_decoder.c
compiling pg_binary_encoder.c
compiling pg_coder.c
compiling pg_connection.c
compiling pg_copy_coder.c
compiling pg_errors.c
compiling pg_result.c
compiling pg_text_decoder.c
compiling pg_text_encoder.c
compiling pg_type_map.c
compiling pg_type_map_all_strings.c
compiling pg_type_map_by_class.c
compiling pg_type_map_by_column.c
compiling pg_type_map_by_mri_type.c
compiling pg_type_map_by_oid.c
compiling pg_type_map_in_ruby.c
compiling util.c
linking shared-object pg_ext.bundle
couldn't understand kern.osversion `14.1.0'
ld: warning: directory not found for option '-L/Users/haven/.sm/pkg/active/lib'
ld: -rpath can only be used when targeting Mac OS X 10.5 or later
collect2: ld returned 1 exit status
Makefile:253: recipe for target 'pg_ext.bundle' failed
make: *** [pg_ext.bundle] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/Apple/.rvm/gems/ruby-2.2.2@/gems/pg-0.18.1 for inspection.
Results logged to /Users/Apple/.rvm/gems/ruby-2.2.2@/extensions/x86_64-darwin-14/2.2.0-static/pg-0.18.1/gem_make.out
An error occurred while installing pg (0.18.1), and Bundler cannot continue.
Make sure that `gem install pg -v '0.18.1'` succeeds before bundling.

Any one can help?

simo
  • 23,342
  • 38
  • 121
  • 218

1 Answers1

0

i had plenty of problems installing pg gem in a fresh SO until i found this:

bundle failing - Can't find the PostgreSQL client library (libpq)

hope this helps you.

Community
  • 1
  • 1
  • this answer here has solved my problem: http://stackoverflow.com/questions/27047463/gem-install-pg-error-couldnt-understand-kern-osversion-14-0-0-on-yosemite-w – simo Aug 12 '15 at 20:25
  • like this: MACOSX_DEPLOYMENT_TARGET=10.9 ARCHFLAGS="-arch x86_64" bundle install --without production – simo Aug 12 '15 at 20:29
  • I got exactly the same error messages (due to a link failure while trying to make pg_ext.bundle), but setting MACOSX_DEPLOYMENT_TARGET didn't work for me. When I upgraded XCode command line tools (based on XCode 7.0.1), I left OSX 10.10.2 in place. I finally downloaded the entire XCode tools, AND upgraded to 10.10.5, and voila -- gem install pg worked. Moral of the story: when installing pg with native extensions, make sure the natives are happy! – Monty Oct 22 '15 at 16:31