When I built the python environment with Anaconda, there was a problem with the environment created with homebrew. I did a lot of research before putting it in, but I didn't know it, so I'll leave it as a rut.
MacOS X Yosemite homebrew, Anaconda ← Danger of mixing
Originally, an environment where you built an environment such as Node.js using homebrew and played with hubot. Recently, I created a Python environment in Anaconda to try out the topic TensorFlow, and started running the tutorial a little.
After a long time hitting the npm command ...
-bash: npm: command not found
What! ??
## help! brew doctor!
A brew doctor in case of trouble. There is a warning.
Warning: Anaconda is known to frequently break Homebrew builds, including Vim and MacVim, due to bundling many duplicates of system and Homebrew-available tools.
If you encounter a build failure please temporarily remove Anaconda from your $PATH and attempt the build again prior to reporting the failure to us. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.
./configure scripts often look for *config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via Homebrew if the config script overrides a system or Homebrew provided script of the same name. We found the following "config" scripts: /Users/spiky00/anaconda/bin/curl-config /Users/spiky00/anaconda/bin/freetype-config /Users/spiky00/anaconda/bin/libdynd-config /Users/spiky00/anaconda/bin/libpng-config /Users/spiky00/anaconda/bin/libpng16-config /Users/spiky00/anaconda/bin/python-config /Users/spiky00/anaconda/bin/python2-config /Users/spiky00/anaconda/bin/python2.7-config /Users/spiky00/anaconda/bin/xml2-config /Users/spiky00/anaconda/bin/xslt-config
Apparently Anaconda uses a config with the same name as Homebrew, which seems to break the build. eh
## solved!
Remove Anaconda from the environment variables and reset the originally set $ PATH.
vi ~/.bash_profile
export PATH="/Users/spiky00/anaconda/bin:$PATH"
Found a snake. And my Node environment is here ...
this…
thus…
export PATH=
This is it!
A neat solution. I haven't tried it yet, but if you change your PATH, you should still be able to use the Anaconda environment.
I was wondering what to do when the environment broke, but I'm glad it was surprisingly easy!
Speaking of which, I think there was some warning when I put in Anaconda ... maybe that ...?
Recommended Posts