No, I'm not saying that you should use MacPorts. That said, it is what I'm most familiar with, and what I recommend because it provides a very usable and quite stable and controlled environment that works for most OS X users. I think of 'brew as a hacker's tool for installing stuff: you really need to know what you're doing to do it right in 'brew. Not very much so in MacPorts. If what you want is just to have GNU Radio (etc) installed for your use, then MacPorts is a good way to go. Even if you want to hack on GNU Radio (etc), using MacPorts is not a bad way to go. If you want to be bleeding-edge, then use 'brew.
As for the command: Quite strange. I was expecting otherwise. Those 'python' files point to the same file, eventually. That means that internal to 'brew some other 'python' is being found. Hmmm ...
Sorry about this but I really have no clue what else to do beyond use MacPorts. If you want to go this route, I -highly- recommend you deinstall all of 'brew first. Because 'brew is installed into /usr/local, its stuff is picked up by many build systems; sometimes this is a blessing but more often than not it is a curse.
- MLD
On Fri, Oct 2, 2015, at 04:53 PM, David Cranor wrote:
OK, so you are saying that I should completely uninstall the homebrew installed gnuradio, then pull, patch, and compile manually?
Here’s the command you asked about.
/Library/Caches/Homebrew> /bin/ls -lAF /usr/local/Cellar/python/2.7.10_2/bin/python /usr/local/bin/python
lrwxr-xr-x 1 davidcranor admin 54 Sep 23 07:35 /usr/local/Cellar/python/2.7.10_2/bin/python@ -> ../Frameworks/Python.framework/Versions/2.7/bin/python
lrwxr-xr-x 1 davidcranor admin 36 Oct 1 18:01 /usr/local/bin/python@ -> ../Cellar/python/2.7.10_2/bin/python