On 5 Feb 2016, at 16:00, Francis Poulin <fpoulin@uwaterloo.ca> wrote:
Yes, I agree that firedrake is installed and can work, but it seems to be using my homebrew version of python, not the firedrake version. To answer the two questions:
** Question 1 **
regular
am-laptop24:software fpoulin$ alias | grep python alias ipython='/usr/local/bin/ipython' alias python='/usr/local/bin/python'
virtualenv
(firedrake)am-laptop24:software fpoulin$ alias | grep python alias ipython='/usr/local/bin/ipython' alias pydoc='python -m pydoc' alias python='/usr/local/bin/python' alias pythonana='/Applications/anaconda/bin/python'
** Question 2 **
regular
am-laptop24:software fpoulin$ type python python is aliased to `/usr/local/bin/python'
virtualenv
(firedrake)am-laptop24:software fpoulin$ type python python is aliased to `/usr/local/bin/python'
OK, great, this is the problem. These alias settings (presumably in your basic or similar) override whatever is in PATH. if you "unalias python" and similarly "unalias ipython" then after activating the virtualenv you should get the correct interpreter. Hopefully with this done you should be good to go! ...
** env stuff **
It seems that to install firedrake my computer us using clang, default C compiler, even though I wanted it to use homebrew. For consistency. On a very minor note, how can one change this?
Homebrew defaults to building all C programs with clang, which we just pick up. See https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Custom-G... for their rationale. In particular, the C++ ABI in the gcc-5 series is no longer compatible with that of clang (at least as of quite recently). As a result, any C++ library that home-brew (or apple provides) which will have been built with clang, must be rebuilt for gcc-5. Cheers, Lawrence