[MacPorts] #43083: py27-scipy @0.13.3: fails to build on OS X 10.7
MacPorts
noreply at macports.org
Fri Apr 11 09:38:53 PDT 2014
#43083: py27-scipy @0.13.3: fails to build on OS X 10.7
------------------------------+--------------------------------
Reporter: Peter.Danecek@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: invalid | Keywords:
Port: py-scipy |
------------------------------+--------------------------------
Comment (by sean@…):
Replying to [comment:9 Peter.Danecek@…]:
> Thanks Sean, your understanding is clear now
>
> I knew there could arise issues from installing libs in System paths
like /usr/local. But honestly I did not think this applies to Python as
well. I assumed the correct "site-packages" to use is determined by the
interpreter you are actually calling, and for a `py27` subport I would
have expected it to be python2.7 from Macports. And I you would like to
use packages at other locations, these would need to be tight in
explicitly.
>
> For the rest: It is very probable that the machine is quite messy, there
were Python versions, related links and variables all over. I purges some
of this stuff, but for sure not all.
Unfortunately, that assumption is wrong. As cal mentioned above, you can
try `port -t` when MacPorts 2.3 comes out (or install from a trunk
checkout). The safer (though, more tedious) approach would be to clean
this system thoroughly. The usual suspects are:
* `/usr/local`
* Ruby packages
* Python packages
* Haskell packages
Sometimes, you can use the `pkg` command to determine what packages were
installed previously. Good luck.
--
Ticket URL: <https://trac.macports.org/ticket/43083#comment:11>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list