#43083: py27-scipy @0.13.3: fails to build on OS X 10.7 ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-scipy | ------------------------------+-------------------------------- Comment (by ryandesign@…): Out of curiosity, what is /opt/local/bin/gfortran, what port installed it, what version is it? Because the port seems to want to use gcc48's gfortran, but if /opt/local/bin/gfortran is something different, that might be a problem. -- Ticket URL: <https://trac.macports.org/ticket/43083#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#43083: py27-scipy @0.13.3: fails to build on OS X 10.7 ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-scipy | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): @ryandesign: You are probably deferring to [http://trac.macports.org/attachment/ticket/43083/py27-scipy.main.log#L3537 L3537] from main.log, right? I checked with my colleague the setup gfortran setup and there seems be nothing strange. `/opt/local/bin/gfortran` points to -> `/opt/local/bin/gfortran-mp-4.8`. The link was created by the `port select` mechanism: {{{ port select gcc Available versions for gcc: gcc42 llvm-gcc42 mp-gcc48 (active) none }}} It is the fortran compiler used normally, is in the $PATH, all normal here. However I guess, the real problem is more related to [http://trac.macports.org/attachment/ticket/43083/py27-scipy.main.log#L3571 L3571], that is numpy.distutils expects a non existing environment variable `FARCHFLAGS` and the exception is not handled. But why: (1) The binary package is not valid? (2) This problem occurs only on the given system? -- Ticket URL: <https://trac.macports.org/ticket/43083#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#43083: py27-scipy @0.13.3: fails to build on OS X 10.7 ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-scipy | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): I attached a main.log from a build with +atlas variant requested. The problem looks identical. -- Ticket URL: <https://trac.macports.org/ticket/43083#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#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 Peter.Danecek@…): Replying to [comment:6 sean@…]:

Unless I am missing something, this is invalid because you are mixing python packages from the system which isn't supported in MacPorts. It seems you have numpy installed into: `/Library/Python/2.7/site-packages /numpy-override`.

Sean, I am not sure I understand your comment completely. Now, that you are pointing to it I see the reference to system `/Library` as well, but I have no idea how it is tight in. You are stating "invalid because you are mixing python packages from the system". But I do not see what I am doing wrong or at least I am not doing this intentionally. When I get to the machine, I will check the content of `/Library/Python/2.7/site-packages/`. But to my understanding, as long as I use MacPort, this content should be ignored, but apparently it is no. So why this ticket is **invalid** ? -- Ticket URL: <https://trac.macports.org/ticket/43083#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#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 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. -- Ticket URL: <https://trac.macports.org/ticket/43083#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X

#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