pg gem 0.15.1 + postgres.app 9.2.4 = more dylib issues #109

Closed
swrobel opened this Issue May 7, 2013 · 76 comments

Comments

Projects
None yet
@swrobel

swrobel commented May 7, 2013

/Users/swrobel/.rvm/gems/ruby-1.9.3-p392@global/gems/polyglot-0.3.3/lib/polyglot.rb:63:in `require': dlopen(/Users/swrobel/.rvm/gems/ruby-1.9.3-p392@cult/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib (LoadError)
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
  Reason: image not found - /Users/swrobel/.rvm/gems/ruby-1.9.3-p392@cult/gems/pg-0.15.1/lib/pg_ext.bundle

I've tried both gem install pg and gem install pg -- --with-pg-config=/Applications/Postgres.app/Contents/MacOS/bin/pg_config and both lead to the same result.

Anyone else seeing this? I'd like to revert to 9.2.2 but I can't find a download link...

@swrobel

This comment has been minimized.

Show comment
Hide comment
@swrobel

swrobel May 7, 2013

Found 9.2.2 here: http://postgres-app.s3.amazonaws.com/PostgresApp-9-2-2-0.zip

Confirmed that downgrading fixed the problem.

swrobel commented May 7, 2013

Found 9.2.2 here: http://postgres-app.s3.amazonaws.com/PostgresApp-9-2-2-0.zip

Confirmed that downgrading fixed the problem.

@jcoby

This comment has been minimized.

Show comment
Hide comment
@jcoby

jcoby May 8, 2013

I had the same issue. Downgrading to 9.2.2 fixed it for me as well.

jcoby commented May 8, 2013

I had the same issue. Downgrading to 9.2.2 fixed it for me as well.

@anthonator

This comment has been minimized.

Show comment
Hide comment
@anthonator

anthonator May 9, 2013

Ran into the same issue.

Ran into the same issue.

@frabrunelle

This comment has been minimized.

Show comment
Hide comment
@frabrunelle

frabrunelle May 10, 2013

I had to downgrade to 9.2.2 as well.

I had to downgrade to 9.2.2 as well.

@rmg

This comment has been minimized.

Show comment
Hide comment
@rmg

rmg May 11, 2013

Another downgrade to 9.2.2 here. Is this related to 0897d9b maybe?

rmg commented May 11, 2013

Another downgrade to 9.2.2 here. Is this related to 0897d9b maybe?

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 12, 2013

Had to downgrade also on my end.

ghost commented May 12, 2013

Had to downgrade also on my end.

@benniemosher

This comment has been minimized.

Show comment
Hide comment
@benniemosher

benniemosher May 13, 2013

I had to downgrade as well.

I had to downgrade as well.

@mech

This comment has been minimized.

Show comment
Hide comment
@mech

mech May 14, 2013

Have the same issue. I need the uuid to play with Rails 4. But when I rake db:drop, the whole thing blow:

dlopen(/Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
Reason: image not found - /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/pg-0.15.1/lib/pg_ext.bundle

The pg gem does install fine. The rails dbconsole works and can query also. Just that migration don't work :(

mech commented May 14, 2013

Have the same issue. I need the uuid to play with Rails 4. But when I rake db:drop, the whole thing blow:

dlopen(/Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
Reason: image not found - /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/pg-0.15.1/lib/pg_ext.bundle

The pg gem does install fine. The rails dbconsole works and can query also. Just that migration don't work :(

@bsy

This comment has been minimized.

Show comment
Hide comment
@bsy

bsy May 14, 2013

Adding the following to my .bash_profile did the trick to fix this loading issue (on rails 3.2.13 + ruby 1.9.3p194) :

export DYLD_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH

bsy commented May 14, 2013

Adding the following to my .bash_profile did the trick to fix this loading issue (on rails 3.2.13 + ruby 1.9.3p194) :

export DYLD_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH

@mech

This comment has been minimized.

Show comment
Hide comment
@mech

mech May 14, 2013

Add @bsy suggestion and it expose another issue with nokogiri :(

dlopen(/Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle, 9): Library not loaded: /usr/local/opt/libxml2/lib/libxml2.2.dylib
Referenced from: /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle
Reason: Incompatible library version: nokogiri.bundle requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 - /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle

I guess it fix some, but not the other similar "dylib" problems.

mech commented May 14, 2013

Add @bsy suggestion and it expose another issue with nokogiri :(

dlopen(/Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle, 9): Library not loaded: /usr/local/opt/libxml2/lib/libxml2.2.dylib
Referenced from: /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle
Reason: Incompatible library version: nokogiri.bundle requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0 - /Users/mech/.rvm/gems/ruby-2.0.0-p0@xx/gems/nokogiri-1.5.9/lib/nokogiri/nokogiri.bundle

I guess it fix some, but not the other similar "dylib" problems.

@bsy

This comment has been minimized.

Show comment
Hide comment
@bsy

bsy May 14, 2013

@mech yeah after I fixed that, I noticed it broke node.js, downgrade it is!

bsy commented May 14, 2013

@mech yeah after I fixed that, I noticed it broke node.js, downgrade it is!

@pda

This comment has been minimized.

Show comment
Hide comment
@pda

pda May 15, 2013

Same problem. Seems the dependency loading in libpq.dylib bundled with Postgres.app is broken, specifically with reference to loading the bundled libssl.

Here's ruby with the system libpq:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/usr/lib/libpq.dylib ruby -v
ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.0]

Here's ruby with the Postgres.app libpq:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib ruby -v
dyld: Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
  Reason: image not found

And an otool dump:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib (compatibility version 5.0.0, current version 5.5.0)
        @executable_path/../lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        @executable_path/../lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

Note that @executable_path/../lib/libssl.1.0.0.dylib is presumably trying to refer to /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib.

Loading just that libssl against ruby results in a similar error:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib ruby -v
dyld: Library not loaded: @executable_path/../lib/libcrypto.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib
  Reason: image not found

Here's the otool dump of that libssl:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libssl.dylib (compatibility version 1.0.0, current version 1.0.0)
        @executable_path/../lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

In this case, @executable_path/../lib/libcrypto.1.0.0.dylib refers to /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib.

Loading just that libcrypto against ruby works fine:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib ruby -v
ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.0]

Presumably that's because it has no more @executable_path references:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

Hope this helps in some way — I'm afraid I have no idea how to help fix it.

pda commented May 15, 2013

Same problem. Seems the dependency loading in libpq.dylib bundled with Postgres.app is broken, specifically with reference to loading the bundled libssl.

Here's ruby with the system libpq:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/usr/lib/libpq.dylib ruby -v
ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.0]

Here's ruby with the Postgres.app libpq:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib ruby -v
dyld: Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
  Reason: image not found

And an otool dump:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib (compatibility version 5.0.0, current version 5.5.0)
        @executable_path/../lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        @executable_path/../lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 6.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

Note that @executable_path/../lib/libssl.1.0.0.dylib is presumably trying to refer to /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib.

Loading just that libssl against ruby results in a similar error:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib ruby -v
dyld: Library not loaded: @executable_path/../lib/libcrypto.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib
  Reason: image not found

Here's the otool dump of that libssl:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libssl.1.0.0.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libssl.dylib (compatibility version 1.0.0, current version 1.0.0)
        @executable_path/../lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

In this case, @executable_path/../lib/libcrypto.1.0.0.dylib refers to /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib.

Loading just that libcrypto against ruby works fine:

pda@paulbook ~ ⸩ DYLD_INSERT_LIBRARIES=/Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib ruby -v
ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.0]

Presumably that's because it has no more @executable_path references:

pda@paulbook ~ ⸩ otool -L /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib
/Applications/Postgres.app/Contents/MacOS/lib/libcrypto.1.0.0.dylib:
        /Applications/Postgres.app/Contents/MacOS/lib/libcrypto.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

Hope this helps in some way — I'm afraid I have no idea how to help fix it.

@pda

This comment has been minimized.

Show comment
Hide comment
@pda

pda May 15, 2013

Also worth noting regarding the bundled OpenSSL build, OPENSSLDIR is hard-coded to /Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl. Maybe related?

pda@paulbook ~ ⸩ /Applications/Postgres.app/Contents/MacOS/bin/openssl version -a | grep OPENSSLDIR
WARNING: can't open config file: /Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl/openssl.cnf
OPENSSLDIR: "/Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl"

pda commented May 15, 2013

Also worth noting regarding the bundled OpenSSL build, OPENSSLDIR is hard-coded to /Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl. Maybe related?

pda@paulbook ~ ⸩ /Applications/Postgres.app/Contents/MacOS/bin/openssl version -a | grep OPENSSLDIR
WARNING: can't open config file: /Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl/openssl.cnf
OPENSSLDIR: "/Users/mattt/Desktop/PostgresApp/Postgres/Vendor/postgres/ssl"
@EnriqueCanals

This comment has been minimized.

Show comment
Hide comment
@EnriqueCanals

EnriqueCanals May 16, 2013

I had the same issue. Downgrading worked for me as well.

dlopen(/Users/enrique/.rvm/gems/ruby-2.0.0-p0@rails-3.2.13/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
Reason: image not found - /Users/enrique/.rvm/gems/ruby-2.0.0-p0@rails-3.2.13/gems/pg-0.15.1/lib/pg_ext.bundle

I had the same issue. Downgrading worked for me as well.

dlopen(/Users/enrique/.rvm/gems/ruby-2.0.0-p0@rails-3.2.13/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
Reason: image not found - /Users/enrique/.rvm/gems/ruby-2.0.0-p0@rails-3.2.13/gems/pg-0.15.1/lib/pg_ext.bundle

@tmcallister

This comment has been minimized.

Show comment
Hide comment
@tmcallister

tmcallister May 16, 2013

Same as above. Downgraded to 9.2.2 to fix. Env: Ruby 2 / Rails 4.

Same as above. Downgraded to 9.2.2 to fix. Env: Ruby 2 / Rails 4.

@dylansm

This comment has been minimized.

Show comment
Hide comment
@dylansm

dylansm May 17, 2013

@tmcallister I downgraded by quitting the app and copying version 9.2.2 over 9.2.4 without issue.

dylansm commented May 17, 2013

@tmcallister I downgraded by quitting the app and copying version 9.2.2 over 9.2.4 without issue.

@iscott

This comment has been minimized.

Show comment
Hide comment
@iscott

iscott May 19, 2013

Thanks @swrobel - had the same issue and downgrading fixed it. Thanks for posting the link!

iscott commented May 19, 2013

Thanks @swrobel - had the same issue and downgrading fixed it. Thanks for posting the link!

@albrow

This comment has been minimized.

Show comment
Hide comment
@albrow

albrow May 20, 2013

I didn't want to downgrade, so after trying a few different solutions I found one that worked for me.

Add the following to your .bash_profile and restart the terminal session.
export DYLD_FALLBACK_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH

It is essentially the same as @bsy's solution but it doesn't screw up other apps that might be depending on DYLD_LIBRARY_PATH.

albrow commented May 20, 2013

I didn't want to downgrade, so after trying a few different solutions I found one that worked for me.

Add the following to your .bash_profile and restart the terminal session.
export DYLD_FALLBACK_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH

It is essentially the same as @bsy's solution but it doesn't screw up other apps that might be depending on DYLD_LIBRARY_PATH.

@HLGgithub

This comment has been minimized.

Show comment
Hide comment
@HLGgithub

HLGgithub May 23, 2013

@stephenalexbrowne your export worked for me... thank you!!

@stephenalexbrowne your export worked for me... thank you!!

@ajb

This comment has been minimized.

Show comment
Hide comment
@ajb

ajb May 24, 2013

another downgrade here. caused a major headache this evening 😢

ajb commented May 24, 2013

another downgrade here. caused a major headache this evening 😢

@andershaig

This comment has been minimized.

Show comment
Hide comment
@andershaig

andershaig May 24, 2013

I just wanted to say thanks @stephenalexbrowne and let others know his solution worked for me as well when some of the other suggestions failed. I also like that it's easily removable when this issue is fixed.

I just wanted to say thanks @stephenalexbrowne and let others know his solution worked for me as well when some of the other suggestions failed. I also like that it's easily removable when this issue is fixed.

@splodingsocks

This comment has been minimized.

Show comment
Hide comment
@splodingsocks

splodingsocks May 24, 2013

@stephenalexbrowne thanks for that temporary fix. EDIT:

Inserting the line:
export DYLD_FALLBACK_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH
in my .zshrc fixes the problem when looking for libssl, but then, when I launch psql I get this error:

dyld: Library not loaded: @executable_path/../lib/libedit.3.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/bin/psql
Reason: image not found

I don't know why this would happen. There's no libedit.3.dylib inside lib. So I don't know why removing that file from my .rc fixes the issue. Any ideas?

I also downgraded, which fixed the loading error, but it wraps an older version of SSL, so I got this back from python:
_psycopg.so requires version 1.0.0 or later, but libssl.0.9.8.dylib provides version 0.9.8

@stephenalexbrowne thanks for that temporary fix. EDIT:

Inserting the line:
export DYLD_FALLBACK_LIBRARY_PATH=/Applications/Postgres.app/Contents/MacOS/lib:$DYLD_LIBRARY_PATH
in my .zshrc fixes the problem when looking for libssl, but then, when I launch psql I get this error:

dyld: Library not loaded: @executable_path/../lib/libedit.3.dylib
Referenced from: /Applications/Postgres.app/Contents/MacOS/bin/psql
Reason: image not found

I don't know why this would happen. There's no libedit.3.dylib inside lib. So I don't know why removing that file from my .rc fixes the issue. Any ideas?

I also downgraded, which fixed the loading error, but it wraps an older version of SSL, so I got this back from python:
_psycopg.so requires version 1.0.0 or later, but libssl.0.9.8.dylib provides version 0.9.8

@memoht

This comment has been minimized.

Show comment
Hide comment
@memoht

memoht May 24, 2013

Ran into exact same problems outlined here. Currently sitting back at 9.2.2.0 until this is sorted out.

memoht commented May 24, 2013

Ran into exact same problems outlined here. Currently sitting back at 9.2.2.0 until this is sorted out.

@lukemelia

This comment has been minimized.

Show comment
Hide comment
@lukemelia

lukemelia May 25, 2013

I'm experiencing the same ilbedit.3.dylib issue as @murphyrandle with the DYLD_FALLBACK_LIBRARY_PATH workaround. It occurs when I try to run psql.

I'm experiencing the same ilbedit.3.dylib issue as @murphyrandle with the DYLD_FALLBACK_LIBRARY_PATH workaround. It occurs when I try to run psql.

@albrow

This comment has been minimized.

Show comment
Hide comment
@albrow

albrow May 26, 2013

@lukemelia and @murphyrandle: I can verify that I have the same problem with psql. Unsetting the env variable seems to fix the issue (but then it breaks rails).

The following command will unset the DYLD_FALLBACK_LIBRARY_PATH environment variable temporarily. It does this by entering a "subshell" which does not alter your current bash environment. After you exit psql it will be set again so that rails (and probably some other things that depend on Postgres.app) will function properly.

(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)

This is assuming that you're using bash and that your .bash_profile is located in your home directory. If that's not the case (or if you're using a .bashrc or other environment setup instead of .bash_profile) change the ~/.bash_profile part of the command to the path to your environment setup script.

If you don't want to type all that out, you can create an alias in your .bash_profile (or equivalent). Something like:

alias psql="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)"

This will automatically and temporarily unset the DYLD_FALLBACK_LIBRARY_PATH when you run psql. It's not ideal, but I tested it and it works for me.

albrow commented May 26, 2013

@lukemelia and @murphyrandle: I can verify that I have the same problem with psql. Unsetting the env variable seems to fix the issue (but then it breaks rails).

The following command will unset the DYLD_FALLBACK_LIBRARY_PATH environment variable temporarily. It does this by entering a "subshell" which does not alter your current bash environment. After you exit psql it will be set again so that rails (and probably some other things that depend on Postgres.app) will function properly.

(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)

This is assuming that you're using bash and that your .bash_profile is located in your home directory. If that's not the case (or if you're using a .bashrc or other environment setup instead of .bash_profile) change the ~/.bash_profile part of the command to the path to your environment setup script.

If you don't want to type all that out, you can create an alias in your .bash_profile (or equivalent). Something like:

alias psql="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)"

This will automatically and temporarily unset the DYLD_FALLBACK_LIBRARY_PATH when you run psql. It's not ideal, but I tested it and it works for me.

@splodingsocks

This comment has been minimized.

Show comment
Hide comment
@splodingsocks

splodingsocks May 26, 2013

That's a great workaround. Thanks!

Murphy Randle
Python Monkey, Space Monkey Inc.
http://www.MurphyRandle.com

On Saturday, May 25, 2013 at 9:31 PM, Alex Browne wrote:

@lukemelia (https://github.com/lukemelia) and @murphyrandle (https://github.com/murphyrandle): I can verify that I have the same problem with psql (and with rails dbconsole). Unsetting the env variable seems to fix the issue (but then it breaks rails).
The following command will unset the DYLD_FALLBACK_LIBRARY_PATH environment variable temporarily. It does this by entering a "subshell" which does not alter your current bash environment. After you exit psql it will be set again so that rails (and probably some other things that depend on Postgres.app) will function properly.
(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)
This is assuming that you're using bash and that your .bash_profile is located in your home directory. If that's not the case (or if you're using a .bashrc or other environment setup instead of .bash_profile) change the ~/.bash_profile part of the command to the path to your environment setup script.
If you don't want to type all that out, you can create an alias in your .bash_profile (or equivalent). Something like:
alias psql="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)" and optionally
alias dbconsole="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; bundle exec rails dbconsole)" if you want to use rails dbconsole.
This will automatically and temporarily unset the DYLD_FALLBACK_LIBRARY_PATH when you run psql or dbconsole. It's not ideal, but I tested it and it works for me.


Reply to this email directly or view it on GitHub (#109 (comment)).

That's a great workaround. Thanks!

Murphy Randle
Python Monkey, Space Monkey Inc.
http://www.MurphyRandle.com

On Saturday, May 25, 2013 at 9:31 PM, Alex Browne wrote:

@lukemelia (https://github.com/lukemelia) and @murphyrandle (https://github.com/murphyrandle): I can verify that I have the same problem with psql (and with rails dbconsole). Unsetting the env variable seems to fix the issue (but then it breaks rails).
The following command will unset the DYLD_FALLBACK_LIBRARY_PATH environment variable temporarily. It does this by entering a "subshell" which does not alter your current bash environment. After you exit psql it will be set again so that rails (and probably some other things that depend on Postgres.app) will function properly.
(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)
This is assuming that you're using bash and that your .bash_profile is located in your home directory. If that's not the case (or if you're using a .bashrc or other environment setup instead of .bash_profile) change the ~/.bash_profile part of the command to the path to your environment setup script.
If you don't want to type all that out, you can create an alias in your .bash_profile (or equivalent). Something like:
alias psql="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; psql)" and optionally
alias dbconsole="(. ~/.bash_profile; unset DYLD_FALLBACK_LIBRARY_PATH; bundle exec rails dbconsole)" if you want to use rails dbconsole.
This will automatically and temporarily unset the DYLD_FALLBACK_LIBRARY_PATH when you run psql or dbconsole. It's not ideal, but I tested it and it works for me.


Reply to this email directly or view it on GitHub (#109 (comment)).

@splodingsocks

This comment has been minimized.

Show comment
Hide comment
@splodingsocks

splodingsocks May 29, 2013

Hmm, so I downloaded the source and did my own build. That seemed to have fixed my problems.

Hmm, so I downloaded the source and did my own build. That seemed to have fixed my problems.

@realdoug

This comment has been minimized.

Show comment
Hide comment
@realdoug

realdoug May 30, 2013

@murphyrandle yea, according to issue #113 it may a problem introduced by this commit: 0897d9b

Is that plausible at all?

@murphyrandle yea, according to issue #113 it may a problem introduced by this commit: 0897d9b

Is that plausible at all?

realdoug referenced this issue May 30, 2013

Use our own OpenSSL build
Apple has deprecated linking to the system provided OpenSSL libraries. In this commit, I added a target that downloads and builds our own copy of OpenSSL. I've also updated the postgresql build script to compile and link against our version of OpenSSL. Additionally, I updated the dylib-target so that it also fixes all the OpenSSL-related paths.
@dylansm

This comment has been minimized.

Show comment
Hide comment
@dylansm

dylansm May 30, 2013

Building it from source worked for me, too. Thanks, @murphyrandle! (Had to do it ...I really like that new retina menu icon....)

dylansm commented May 30, 2013

Building it from source worked for me, too. Thanks, @murphyrandle! (Had to do it ...I really like that new retina menu icon....)

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob May 30, 2013

Member

The reason for the dylib troubles are the way we defined the paths. When we link libpq to libssl, we could use a path like /Applications/Postgres.app/Contents/MacOS/lib/libssl.dylib, but then Postgres.app would only work if you moved it to your Applications folder. We want Postgres.app to also work when the user opens it directly from the Downloads folder, so we use a relative path like @executable_path/../lib/libssl.dylib. This works great for the postgres and psql binaries inside the Postgres.app package. But it doesn't work when something outside of the package, like a ruby gem, wants to use our libraries -- because then the relative path from executable to library isn't correct anymore.

I think @harrijauri might have a solution for this problem in this commit: https://github.com/harrijauri/PostgresApp/commit/25c4914d5662f8248e529b249e2beb6ec80507ed
His solution is to use @loader_path instead of @executable_path. Unfortunately, his solution is written in a ruby script, which is a bit hard to understand for me, so I'm not totally sure what he does, but it might fix this problem. I'll have a look.

Member

jakob commented May 30, 2013

The reason for the dylib troubles are the way we defined the paths. When we link libpq to libssl, we could use a path like /Applications/Postgres.app/Contents/MacOS/lib/libssl.dylib, but then Postgres.app would only work if you moved it to your Applications folder. We want Postgres.app to also work when the user opens it directly from the Downloads folder, so we use a relative path like @executable_path/../lib/libssl.dylib. This works great for the postgres and psql binaries inside the Postgres.app package. But it doesn't work when something outside of the package, like a ruby gem, wants to use our libraries -- because then the relative path from executable to library isn't correct anymore.

I think @harrijauri might have a solution for this problem in this commit: https://github.com/harrijauri/PostgresApp/commit/25c4914d5662f8248e529b249e2beb6ec80507ed
His solution is to use @loader_path instead of @executable_path. Unfortunately, his solution is written in a ruby script, which is a bit hard to understand for me, so I'm not totally sure what he does, but it might fix this problem. I'll have a look.

@dfuentes77

This comment has been minimized.

Show comment
Hide comment
@dfuentes77

dfuentes77 Jun 1, 2013

same here, reverted to 9.2.2.0

same here, reverted to 9.2.2.0

@jwaldrip

This comment has been minimized.

Show comment
Hide comment
@jwaldrip

jwaldrip Jun 1, 2013

I am reverting to hombrew until a more stable product can be delivered. Please keep me informed.

jwaldrip commented Jun 1, 2013

I am reverting to hombrew until a more stable product can be delivered. Please keep me informed.

@gverri

This comment has been minimized.

Show comment
Hide comment
@gverri

gverri Jun 6, 2013

Is 9.2.2 working fine for you? Or should I go back to default?

gverri commented Jun 6, 2013

Is 9.2.2 working fine for you? Or should I go back to default?

@pruett

This comment has been minimized.

Show comment
Hide comment
@pruett

pruett Jun 6, 2013

+1 for downgrading to 9.2.2.0; fixed the following issues (Rails 3.2.13):

dlopen(/Users/pruett/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
  Reason: image not found - /Users/pruett/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle

pruett commented Jun 6, 2013

+1 for downgrading to 9.2.2.0; fixed the following issues (Rails 3.2.13):

dlopen(/Users/pruett/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @executable_path/../lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/lib/libpq.dylib
  Reason: image not found - /Users/pruett/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle
@splodingsocks

This comment has been minimized.

Show comment
Hide comment
@splodingsocks

splodingsocks Jun 7, 2013

So, is anybody maintaining this app still?
And thanks for the great answer, @jakob

So, is anybody maintaining this app still?
And thanks for the great answer, @jakob

@vamshionrails

This comment has been minimized.

Show comment
Hide comment
@vamshionrails

vamshionrails Jun 13, 2013

Simply do

sudo ln -s /Library/Postgresql/9.2/lib/libpq.5.dylib /usr/lib/libpq.5.dylib

Vamshi

Simply do

sudo ln -s /Library/Postgresql/9.2/lib/libpq.5.dylib /usr/lib/libpq.5.dylib

Vamshi

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jun 18, 2013

Member

I'm sorry for taking so long to find a fix for this issue, after all I caused the problem by boundling openssl. (which is a good thing, if it wouldn't break the pg gem)

I have now made a beta build of 9.2.4 to address this issue. Could somebody try if this beta fixes the issue?
https://s3-eu-west-1.amazonaws.com/eggerapps.at/postgresapp/PostgresApp-Core-9.2.4-Beta1.zip

Note: This beta includes PostgreSQL core only (no PostGIS, no plv8)

Member

jakob commented Jun 18, 2013

I'm sorry for taking so long to find a fix for this issue, after all I caused the problem by boundling openssl. (which is a good thing, if it wouldn't break the pg gem)

I have now made a beta build of 9.2.4 to address this issue. Could somebody try if this beta fixes the issue?
https://s3-eu-west-1.amazonaws.com/eggerapps.at/postgresapp/PostgresApp-Core-9.2.4-Beta1.zip

Note: This beta includes PostgreSQL core only (no PostGIS, no plv8)

@memoht

This comment has been minimized.

Show comment
Hide comment
@memoht

memoht Jun 18, 2013

I just downloaded the Beta and was able to successfully fire up my Rails apps and connect to the database, so it appears this is working. I'll run with it for a bit and see if it works out. Thanks for working on resolving this issue.

memoht commented Jun 18, 2013

I just downloaded the Beta and was able to successfully fire up my Rails apps and connect to the database, so it appears this is working. I'll run with it for a bit and see if it works out. Thanks for working on resolving this issue.

@henrrrik

This comment has been minimized.

Show comment
Hide comment
@henrrrik

henrrrik Jun 18, 2013

Beta works for me too.

Beta works for me too.

@gverri

This comment has been minimized.

Show comment
Hide comment
@gverri

gverri Jun 18, 2013

Seems to be working here too.

gverri commented Jun 18, 2013

Seems to be working here too.

@dotpao

This comment has been minimized.

Show comment
Hide comment
@dotpao

dotpao Jun 19, 2013

Beta version works fine

dotpao commented Jun 19, 2013

Beta version works fine

@hadiS

This comment has been minimized.

Show comment
Hide comment
@hadiS

hadiS Jun 19, 2013

Beta works for me.

hadiS commented Jun 19, 2013

Beta works for me.

@cmattson

This comment has been minimized.

Show comment
Hide comment
@cmattson

cmattson Jun 19, 2013

Beta's working fine here too.

Beta's working fine here too.

@JacobEvelyn

This comment has been minimized.

Show comment
Hide comment
@JacobEvelyn

JacobEvelyn Jun 20, 2013

Beta works for me too.

Beta works for me too.

@motymichaely

This comment has been minimized.

Show comment
Hide comment
@motymichaely

motymichaely Jun 20, 2013

Beta works for me too.

Beta works for me too.

@wycats

This comment has been minimized.

Show comment
Hide comment
@wycats

wycats Jun 21, 2013

@jakob is the solution to use @loader_path. I hit these issues when trying to use Postgres.app with Tokaido and was able to resolve them via @loader_path.

wycats commented Jun 21, 2013

@jakob is the solution to use @loader_path. I hit these issues when trying to use Postgres.app with Tokaido and was able to resolve them via @loader_path.

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jun 21, 2013

Member

@wycats yes, the solution uses @loader_path. The beta is just a build of commit 1fa960e referenced above. I'm very busy at the moment, as soon as I have time I will finish the refactoring so the extensions (PostGIS, plv8) are compiled as well.

Member

jakob commented Jun 21, 2013

@wycats yes, the solution uses @loader_path. The beta is just a build of commit 1fa960e referenced above. I'm very busy at the moment, as soon as I have time I will finish the refactoring so the extensions (PostGIS, plv8) are compiled as well.

@wycats

This comment has been minimized.

Show comment
Hide comment
@wycats

wycats Jun 21, 2013

@jakob Awesome. Tokaido works great with the beta! I'm excited for people to be able to use Tokaido+Postgres.app to get Rails apps running quickly with little hassle.

I posted about my progress at:

wycats commented Jun 21, 2013

@jakob Awesome. Tokaido works great with the beta! I'm excited for people to be able to use Tokaido+Postgres.app to get Rails apps running quickly with little hassle.

I posted about my progress at:

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jun 22, 2013

Having the same issue. Downgrading to 9.2.2 fixed it.
Add retina icon for status bar manually : )

ghost commented Jun 22, 2013

Having the same issue. Downgrading to 9.2.2 fixed it.
Add retina icon for status bar manually : )

@Yenwod

This comment has been minimized.

Show comment
Hide comment
@Yenwod

Yenwod Jun 23, 2013

the beta works for me, too

Yenwod commented Jun 23, 2013

the beta works for me, too

@Albertc

This comment has been minimized.

Show comment
Hide comment
@Albertc

Albertc Jun 26, 2013

Forgive my ignorance, but in my case don't know how to solve.

I have Postgres Database installed in my Mac OSX ML, with "Postgres Admin", but without any Postgres.app file

Database Server: PostgresSQL v9.1.9.1

With other projects with Rails 3.0.9, gem 'pg' works fine with gem pg '0.14.1'.
Now with Rails 4, and Ruby 2, I get this error every time I run rake command.

How can I downgrade to 9.2.2 version?, where is the file to change?

Thanks you

Albertc commented Jun 26, 2013

Forgive my ignorance, but in my case don't know how to solve.

I have Postgres Database installed in my Mac OSX ML, with "Postgres Admin", but without any Postgres.app file

Database Server: PostgresSQL v9.1.9.1

With other projects with Rails 3.0.9, gem 'pg' works fine with gem pg '0.14.1'.
Now with Rails 4, and Ruby 2, I get this error every time I run rake command.

How can I downgrade to 9.2.2 version?, where is the file to change?

Thanks you

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jun 26, 2013

Member

@Albertc The problem and solution(s) discussed on this page apply only if you installed "Postgres.app" (If you did, it should be in your /Applications/ folder. If you didn't, your problem is unrelated.) To downgrade, just download the old version or the beta (see links above) and replace Postgres.app

Member

jakob commented Jun 26, 2013

@Albertc The problem and solution(s) discussed on this page apply only if you installed "Postgres.app" (If you did, it should be in your /Applications/ folder. If you didn't, your problem is unrelated.) To downgrade, just download the old version or the beta (see links above) and replace Postgres.app

@Albertc

This comment has been minimized.

Show comment
Hide comment
@Albertc

Albertc Jun 26, 2013

You are right, I was lost, thanks you.
I solved the problem just correcting the folder of gem install configuration: gem install pg -- --with-pg-config=/opt/local/lib/POSTGRESQL91/bin/pg_config

  • Seems than when you write you own problems, the solutions comes alone. Sorry for the inconvenience

Albertc commented Jun 26, 2013

You are right, I was lost, thanks you.
I solved the problem just correcting the folder of gem install configuration: gem install pg -- --with-pg-config=/opt/local/lib/POSTGRESQL91/bin/pg_config

  • Seems than when you write you own problems, the solutions comes alone. Sorry for the inconvenience
@vitamino

This comment has been minimized.

Show comment
Hide comment
@vitamino

vitamino Jun 28, 2013

The beta is ok :) Thank you!

The beta is ok :) Thank you!

@swrobel

This comment has been minimized.

Show comment
Hide comment
@swrobel

swrobel Jul 10, 2013

And at least, I'll verify as the original reporter that the beta works. New release coming soon?

swrobel commented Jul 10, 2013

And at least, I'll verify as the original reporter that the beta works. New release coming soon?

@craigkerstiens

This comment has been minimized.

Show comment
Hide comment
@craigkerstiens

craigkerstiens Jul 10, 2013

Member

👍 for shipping a new release

Member

craigkerstiens commented Jul 10, 2013

👍 for shipping a new release

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jul 15, 2013

Member

Good to hear beta 1 is working for everyone. I made a new beta that includes PostGIS and PLV8. Could someone please test Beta 2? I think if this beta works we can ship a new release.

Download Link Beta 2: https://s3-eu-west-1.amazonaws.com/eggerapps.at/postgresapp/PostgresApp-9.2.4.3-Beta2.zip

Member

jakob commented Jul 15, 2013

Good to hear beta 1 is working for everyone. I made a new beta that includes PostGIS and PLV8. Could someone please test Beta 2? I think if this beta works we can ship a new release.

Download Link Beta 2: https://s3-eu-west-1.amazonaws.com/eggerapps.at/postgresapp/PostgresApp-9.2.4.3-Beta2.zip

@pda

This comment has been minimized.

Show comment
Hide comment
@pda

pda Jul 15, 2013

Beta 2 seems fine to me.
I'm using hstore but not PostGIS or PLV8.

pda commented Jul 15, 2013

Beta 2 seems fine to me.
I'm using hstore but not PostGIS or PLV8.

@swrobel

This comment has been minimized.

Show comment
Hide comment
@swrobel

swrobel Jul 15, 2013

Just tried Beta 2 and for some reason it wasn't seeing any of my existing DBs that I had set up in Beta 1. Went back to Beta 1 and they're all there.

swrobel commented Jul 15, 2013

Just tried Beta 2 and for some reason it wasn't seeing any of my existing DBs that I had set up in Beta 1. Went back to Beta 1 and they're all there.

@memoht

This comment has been minimized.

Show comment
Hide comment
@memoht

memoht Jul 16, 2013

I also just tried Beta 2 and it did not see my existing databases. Went back to previous beta and they are there.

memoht commented Jul 16, 2013

I also just tried Beta 2 and it did not see my existing databases. Went back to previous beta and they are there.

@pda

This comment has been minimized.

Show comment
Hide comment
@pda

pda Jul 16, 2013

Same; I had no databases after the upgrade, but that didn't bother me, I re-created them.

According to lsof | grep postgres, the new beta 2 seems to be storing data in:

~/Library/Containers/com.heroku.postgres/Data/Library/Application Support/Postgres/var/base/16387

pda commented Jul 16, 2013

Same; I had no databases after the upgrade, but that didn't bother me, I re-created them.

According to lsof | grep postgres, the new beta 2 seems to be storing data in:

~/Library/Containers/com.heroku.postgres/Data/Library/Application Support/Postgres/var/base/16387
@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jul 16, 2013

Member

Thanks for the reports. The difference is that Beta 2 is sandboxed, Beta 1 (and the versions from postgresapp.com) are not sandboxed. Therefore they store data in different directories.

Non-Sandboxed version:
~/Library/Application Support/Postgres

Sandboxed version:
~/Library/Containers/com.heroku.postgres/Data/Library/Application Support/Postgres

The release version will again not be sandboxed.

Member

jakob commented Jul 16, 2013

Thanks for the reports. The difference is that Beta 2 is sandboxed, Beta 1 (and the versions from postgresapp.com) are not sandboxed. Therefore they store data in different directories.

Non-Sandboxed version:
~/Library/Application Support/Postgres

Sandboxed version:
~/Library/Containers/com.heroku.postgres/Data/Library/Application Support/Postgres

The release version will again not be sandboxed.

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Aug 27, 2013

Member

Release is out. Hopefully this finally fixes this longstanding issue.
Download it here:
https://github.com/PostgresApp/PostgresApp/releases/tag/9.2.4.3

Member

jakob commented Aug 27, 2013

Release is out. Hopefully this finally fixes this longstanding issue.
Download it here:
https://github.com/PostgresApp/PostgresApp/releases/tag/9.2.4.3

@jakob jakob closed this Aug 27, 2013

@scmx

This comment has been minimized.

Show comment
Hide comment
@scmx

scmx Aug 27, 2013

@jakob, I get this:

$ psql
dyld: Library not loaded: /Users/jakob/Documents/pg92/src/../Postgres/Vendor/postgres/lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/bin/psql
  Reason: image not found
[1]    1137 trace trap  psql

scmx commented Aug 27, 2013

@jakob, I get this:

$ psql
dyld: Library not loaded: /Users/jakob/Documents/pg92/src/../Postgres/Vendor/postgres/lib/libssl.1.0.0.dylib
  Referenced from: /Applications/Postgres.app/Contents/MacOS/bin/psql
  Reason: image not found
[1]    1137 trace trap  psql
@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Aug 27, 2013

Member

Yes, I managed to upload a broken build. I'm sorry. Fixed version is already up again.

Member

jakob commented Aug 27, 2013

Yes, I managed to upload a broken build. I'm sorry. Fixed version is already up again.

@swrobel

This comment has been minimized.

Show comment
Hide comment
@swrobel

swrobel Aug 27, 2013

Fixed build is working

swrobel commented Aug 27, 2013

Fixed build is working

@splodingsocks

This comment has been minimized.

Show comment
Hide comment

Thank you!

@kylefritz

This comment has been minimized.

Show comment
Hide comment
@kylefritz

kylefritz Sep 9, 2013

💣 work guys!!!

💣 work guys!!!

@dfuentes77

This comment has been minimized.

Show comment
Hide comment
@dfuentes77

dfuentes77 Sep 9, 2013

downloaded the app on latest Lion and it won't launch, it keeps crashing

downloaded the app on latest Lion and it won't launch, it keeps crashing

@dfuentes77

This comment has been minimized.

Show comment
Hide comment
@schmielson

This comment has been minimized.

Show comment
Hide comment
@schmielson

schmielson Oct 23, 2013

FWIW: I'm unable to run the current release (9.3.0) on Mac OS X Mavericks. I had to downgrade to 9.2.2.0 as mentioned above. 9.2.4.3 did not work for me.

FWIW: I'm unable to run the current release (9.3.0) on Mac OS X Mavericks. I had to downgrade to 9.2.2.0 as mentioned above. 9.2.4.3 did not work for me.

@leods92

This comment has been minimized.

Show comment
Hide comment
@leods92

leods92 Oct 23, 2013

Running 9.2.4.4 on Mavericks just fine.

leods92 commented Oct 23, 2013

Running 9.2.4.4 on Mavericks just fine.

@schmielson

This comment has been minimized.

Show comment
Hide comment
@schmielson

schmielson Oct 23, 2013

@leods92 thanks for the heads-up. Interesting - I just gave 9.2.4.4 a whirl and I get a dylib failure:

rake aborted!
dlopen(/Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @loader_path/../lib/libpq.5.dylib
  Referenced from: /Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle
  Reason: image not found - /Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle

Strange. Back to 9.2.2.0 for now...

@leods92 thanks for the heads-up. Interesting - I just gave 9.2.4.4 a whirl and I get a dylib failure:

rake aborted!
dlopen(/Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle, 9): Library not loaded: @loader_path/../lib/libpq.5.dylib
  Referenced from: /Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle
  Reason: image not found - /Users/[USERNAME]/.rbenv/versions/2.0.0-p195/lib/ruby/gems/2.0.0/gems/pg-0.15.1/lib/pg_ext.bundle

Strange. Back to 9.2.2.0 for now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment