Summary: | dev-python/numpy-1.1.1 - sandbox violation mkdir: /root/.sunstudio | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matyukevich Sergey <geomatsi> |
Component: | [OLD] Development | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | geomatsi, python |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | complete output of "emerge -vu numpy" |
Description
Matyukevich Sergey
2008-09-13 06:57:26 UTC
Created attachment 165318 [details]
complete output of "emerge -vu numpy"
just in case I attached the complete log of emerge -vu numpy
Hi, numpy does not do anything about sunstudio, it is probably sunstudio itself trying to write down some user config options. We won't make a special case for sunstudio in the numpy ebuild. numpy distutils looks for a fortran compiler, and the first one to find on your path is f77 from sunstudio. We are not (yet) supporting sunstudio in the tree, so the fortran eclass cannot guess it. I would suggest to try something like F77=gfortran emerge numpy and see whether you can avoid sunstudio to be the first fortran compiler choice. Hi, So the problem was in my workaround - no proper value for the fortran environment variables. I tried the solution suggested by Sebastian, but also added F90: F77=gfortran F90=gfortran emerge -vu numpy The result was fine: numpy was succesfully installed. Besides - I checked - it was operational :) My suggestion would be to close/reject this bug. If it is necessary to indicate the reason, that would be "user configuration issue". Thanks for checking. Closing then.
> F77=gfortran F90=gfortran emerge -vu numpy
NB: f90 variable is usually FC, not F90.
|