[Numpy-discussion] atlas not found, why?
Fri Nov 7 05:23:35 CST 2008
On Fri, Nov 7, 2008 at 8:10 PM, T J <firstname.lastname@example.org> wrote:
> On Fri, Nov 7, 2008 at 2:16 AM, David Cournapeau
> <email@example.com> wrote:
>> And you have no site.cfg at all ?
> Wow. I was too focused on the current directory and didn't realize I
> had an old site.cfg in ~/.
> Two points:
> 1) Others (myself included) might catch such silliness sooner if the
> location of the cfg file were printed to screen during setup.py. As
> of now, I get
I agree this is confusing. Our build process generally produces way
too much output, and not always useful information. FOr the site.cfg,
there are a lot of possibilities, I think the whole process is a bit
too smart for its own good, but it is hard to change without breaking
someone else workflow.
I will take a look at the code to see if it is doable to print the
actual site.cfg used if it is indeed used.
> Running from numpy source directory.
> non-existing path in 'numpy/distutils': 'site.cfg'
> F2PY Version 2_5986
> 2) The current system_info.py says:
> The file 'site.cfg' is looked for in
> 1) Directory of main setup.py file being run.
> 2) Home directory of user running the setup.py file as ~/.numpy-site.cfg
> 3) System wide directory (location of this file...)
> Doesn't this mean that it should *not* have picked up my ~/site.cfg?
Yes, it seems. To be honest, I never used this feature, I am surprised
myself it picked up $HOME/site.cfg.
> Anyway, I can now report that ATLAS is detected without defining any
> environment variables.
This the fortran wrappers of the ATLAS are broken, I am not sure it is
such a great news :)
More information about the Numpy-discussion