How to resolve “dyld: Library not loaded: @executable_path..” error

Question

I was trying to check the AWS-CLI version on my MAC OS X. And the below error hit back:

dyld: Library not loaded: @executable_path/../.Python
  Referenced from: /usr/local/aws/bin/python
  Reason: image not found
Abort trap: 6

Any relevant inputs on how to fix this would be highly appreciated.

Answer 1

It is a bug with awscli and it might be fixed with the next versions. That's why, a best practices is to upgrade :

brew upgrade awscli

Answer 2

You must have messed up with the brew. Try reinstalling it using: brew install awscli (followed by brew link awscli if needed).

Answer 3

This error occurs because your virtual environment has broken symlinks. Here is a nice solution. https://gist.github.com/tevino/1a557a0c200d61d4e4fb

Also, here is a similar question: Broken references in Virtualenvs

Answer 4

I had similar issue while installing awscli with homebrew on mac. So final approach was "brew uninstall python3" and reinstall awscli again.

Answer 5

If you have already python (python --version works. If not install it with brew install python). It works for me:

1. Uninstall aws

   $ sudo rm -rf /usr/local/aws
   $ sudo rm /usr/local/bin/aws
   

2. Install it again

   $ curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"
   $ unzip awscli-bundle.zip
   $ sudo ./awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws
   

Answer 6

I had it installed through curl, the regular way

$ curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"

Then it stopped working complaining about not finding python2.7

dyld: Library not loaded: @executable_path/../.Python
  Referenced from: /usr/local/aws/bin/python2.7
  Reason: image not found
Abort trap: 6

so I fixed it by following these steps (make sure you don't do this if you installed it through brew):

$ sudo rm -rf /usr/local/aws
$ sudo rm /usr/local/bin/aws

Then I installed it using brew:

$ brew upgrade
$ brew install awscli

Answer 7

It's possible to trigger this error by having a problem in your virtualenv. For example, I had an existing working virtualenv and ran brew install awscli and it broke my virtualenv with this error. If that's the case, deleting and recreating your virtualenv (the same way you originally created it) should resolve the problem. It did for me.