Building Numpy Windows Superpack
Greetings, I have been trying to build the numpy superpack on windows using the binaries posted by David. Unfortunately, I haven't even been able to correctly write the site.cfg file to locate all three sets of binaries needed for the superpack. When I manually specify to use only the sse3 binaries, I can get numpy to build from trunk, but it fails miserably when running the test suite. In fact, in python26, the tests freeze python and causes it to exit. I figured I'd try to get this set up correctly before even trying to compile the cpucaps nsis plugin. If someone has successfully used David's binaries would they be willing to share their site.cfg? Thanks in advance. Patrick -- Patrick Marsh Ph.D. Student / NSSL Liaison to the HWT School of Meteorology / University of Oklahoma Cooperative Institute for Mesoscale Meteorological Studies National Severe Storms Laboratory http://www.patricktmarsh.com
Hi Patrick, On Sun, Feb 28, 2010 at 1:35 PM, Patrick Marsh <patrickmarshwx@gmail.com> wrote:
Greetings, I have been trying to build the numpy superpack on windows using the binaries posted by David.
Could you post *exactly* the sequence of commands you executed ? Especially at the beginning, building things can be frustrating because the cause of failures can be hard to diagnose. FWIW, I've just built the nosse version with mingw on windows 7, there was no issue at all, cheers, David
Hi David, There really isn't much in the way of commands that I've used - I haven't gotten that far. So far, I've downloaded your binaries and then attempted to set up my numpy site.cfg file to use your binaries. I used the following as my site.cfg [atlas] library_dirs = d:\svn\BlasLapack\binaries\nosse,d:\svn\BlasLapack\binaries\sse2,d:\svn\BlasLapack\binaries\sse3 atlas_libs = lapack, f77blas, cblas, atlas However, when invoking 'setup.py config' it won't recognize a list of directories, even though the example site.cfg has an example with one. As soon as I don't use a list of paths and only use one of them, I can get setup.py bdist_wininst to run without error. I'm going to play around with the paver script and follow Ralf's instructions in the previous example and see what happens. Patrick On Sun, Feb 28, 2010 at 4:31 AM, David Cournapeau <cournape@gmail.com>wrote:
Hi Patrick,
On Sun, Feb 28, 2010 at 1:35 PM, Patrick Marsh <patrickmarshwx@gmail.com> wrote:
Greetings, I have been trying to build the numpy superpack on windows using the binaries posted by David.
Could you post *exactly* the sequence of commands you executed ? Especially at the beginning, building things can be frustrating because the cause of failures can be hard to diagnose.
FWIW, I've just built the nosse version with mingw on windows 7, there was no issue at all,
cheers,
David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- Patrick Marsh Ph.D. Student / NSSL Liaison to the HWT School of Meteorology / University of Oklahoma Cooperative Institute for Mesoscale Meteorological Studies National Severe Storms Laboratory http://www.patricktmarsh.com
Patrick Marsh wrote:
Hi David,
There really isn't much in the way of commands that I've used - I haven't gotten that far. So far, I've downloaded your binaries and then attempted to set up my numpy site.cfg file to use your binaries. I used the following as my site.cfg
[atlas] library_dirs = d:\svn\BlasLapack\binaries\nosse,d:\svn\BlasLapack\binaries\sse2,d:\svn\BlasLapack\binaries\sse3 atlas_libs = lapack, f77blas, cblas, atlas
However, when invoking 'setup.py config' it won't recognize a list of directories, even though the example site.cfg has an example with one.
First, you should not put the three paths into library_dirs, it does not make much sense here (I am not sure what distutils does exactly in this case, whether it took the first path or the last one, but it will only take into account one). Then, I would advise to bypass site.cfg altogether, and just use env variables, as done in the paver script. E.g.: set LAPACK=d:\svn\BlasLapack\binaries\nosse python setup.py build -c mingw32 bdist_wininst because then you can easily control which one gets included from the command line. It is also much easier to script it this way.
I'm going to play around with the paver script and follow Ralf's instructions in the previous example and see what happens.
In general, you should use the paver script as a reference. It contains a lot of small best-practice things I have ended up after quite a while. cheers, David
On Sun, Feb 28, 2010 at 12:35 PM, Patrick Marsh <patrickmarshwx@gmail.com>wrote:
Greetings,
I have been trying to build the numpy superpack on windows using the binaries posted by David. Unfortunately, I haven't even been able to correctly write the site.cfg file to locate all three sets of binaries needed for the superpack. When I manually specify to use only the sse3 binaries, I can get numpy to build from trunk, but it fails miserably when running the test suite. In fact, in python26, the tests freeze python and causes it to exit. I figured I'd try to get this set up correctly before even trying to compile the cpucaps nsis plugin.
If someone has successfully used David's binaries would they be willing to share their site.cfg? Thanks in advance.
I haven't been able to finish the binaries just yet, but I got this to work. Without needing a site.cfg file, the paver script should be enough. In pavement.py: NOSSE_CFG = {'BLAS': r'/Users/rgommers/.wine/drive_c/local/bin/yop/nosse', 'LAPACK': r'/Users/rgommers/.wine/drive_c/local/bin/yop/nosse'} Then: $ paver bdist_superpack <SNIP> FOUND: libraries = ['lapack', 'blas'] library_dirs = ['/Users/rgommers/.wine/drive_c/local/bin/yop/nosse'] define_macros = [('NO_ATLAS_INFO', 1)] language = f77 <etc> Cheers, Ralf
participants (4)
-
David Cournapeau -
David Cournapeau -
Patrick Marsh -
Ralf Gommers