[Numpy-svn] r6540 - trunk
Tue Mar 3 05:58:03 CST 2009
Date: 2009-03-03 05:57:57 -0600 (Tue, 03 Mar 2009)
New Revision: 6540
Add notes on Windows for AMD64.
--- trunk/INSTALL.txt 2009-03-03 11:57:45 UTC (rev 6539)
+++ trunk/INSTALL.txt 2009-03-03 11:57:57 UTC (rev 6540)
@@ -91,3 +91,44 @@
sudo apt-get install atlas3-sse2
+Windows 64 bits notes
+Note: only AMD64 is supported (IA64 is not) - AMD64 is the version most people
+Free compilers (mingw-w64)
+To use the free compilers (mingw-w64), you need to build your own toolchain, as
+the mingw project only distribute cross-compilers (cross-compilation is not
+supported by numpy). Since this toolchain is still being worked on, serious
+compilers bugs can be expected. binutil 2.19 + gcc 4.3.3 + mingw-w64 runtime
+gives you a working C compiler (but the C++ is broken). gcc 4.4 will hopefully
+be able to run natively.
+This is the only tested way to get a numpy with a FULL blas/lapack (scipy does
+not work because of C++).
+If you are familiar with MS tools, that's obviously the easiest path, and the
+compilers are hopefully more mature (although in my experience, they are quite
+fragile, and often segfault on invalid C code). The main drawback is that no
+fortran compiler + MS compiler combination has been tested - mingw-w64 gfortran
++ MS compiler does not work at all (it is unclear whether it ever will).
+For python 2.5, you need VS 2005 (MS compiler version 14) targetting
+AMD64 bits, or the Platform SDK v6.0 or below (which gives command
+line versions of 64 bits target compilers). The PSDK is free.
+For python 2.6, you need VS 2008. The freely available version does not
+contains 64 bits compilers (you also need the PSDK, v6.1).
+It is *crucial* to use the right version: python 2.5 -> version 14, python 2.6,
+version 15. You can check the compiler version with cl.exe /?. Note also that
+for python 2.5, 64 bits and 32 bits versions use a different compiler version.
More information about the Numpy-svn