Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-24 Thread Ralf Gommers
On Wed, Feb 24, 2010 at 3:42 PM, David Cournapeau courn...@gmail.comwrote:


 So here is how I see things in the near future for release:
 - compile a simple binary installer for mac os x and windows (no need
 for doc or multiple archs) from 1.4.x
 - test this with the scipy binary out there (running the full test
 suites), ideally other well known packages as well (matplotlib,
 pytables, etc...).
 - if it works for you, or you cannot easily test it, put it for wide
 testing as a basis for the 1.4.0.1 binary
 - if it works, make a RC1 for Numpy 1.4.0.1 (full binaries).

 I think we need to push this ASAP to recover from the current
 confusion w.r.t. binaries.

 That's a sensible plan, I'll start on it right away.

Just to double-check, can the 1.4.x branch be released as-is? How about the
version, the version scheme major.minor.micro does not allow for your
proposed 1.4.0.1. Do you want to just drop the last .1 or make this 1.4.1?


Patrick, are you okay with David's plan as well? Do you want to do this in
parallel so we both generate a complete set of binaries?

Cheers,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-24 Thread David Cournapeau
Ralf Gommers wrote:
 On Wed, Feb 24, 2010 at 3:42 PM, David Cournapeau courn...@gmail.com 
 mailto:courn...@gmail.com wrote:
 
 
 So here is how I see things in the near future for release:
 - compile a simple binary installer for mac os x and windows (no need
 for doc or multiple archs) from 1.4.x
 - test this with the scipy binary out there (running the full test
 suites), ideally other well known packages as well (matplotlib,
 pytables, etc...).
 - if it works for you, or you cannot easily test it, put it for wide
 testing as a basis for the 1.4.0.1 binary
 - if it works, make a RC1 for Numpy 1.4.0.1 (full binaries).
 
 I think we need to push this ASAP to recover from the current
 confusion w.r.t. binaries.
 
 That's a sensible plan, I'll start on it right away.

Great. Let me know of any glitch.

 Just to double-check, can the 1.4.x branch be released as-is? How about 
 the version, the version scheme major.minor.micro does not allow for 
 your proposed 1.4.0.1. Do you want to just drop the last .1 or make this 
 1.4.1?

Yes, 1.4.1 is fine. There are a few fixes besides the ABI fix now, so no 
need to complicate things further.

I think 1.4.x can serve as the basis for 1.4.1 as is. I have not checked 
recently if it builds OK on MS compiler, but not much has changed.

cheers,

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-24 Thread Patrick Marsh
This sounds good to me.  I also like the idea of doing this in parallel so
we both have a complete set of binaries - at least on the Windows side.  I'm
still having issues with my MBP, but hope to have those resolved later
today.

Patrick




On Wed, Feb 24, 2010 at 4:45 AM, Ralf Gommers
ralf.gomm...@googlemail.comwrote:

 On Wed, Feb 24, 2010 at 3:42 PM, David Cournapeau courn...@gmail.comwrote:


 So here is how I see things in the near future for release:
 - compile a simple binary installer for mac os x and windows (no need
 for doc or multiple archs) from 1.4.x
 - test this with the scipy binary out there (running the full test
 suites), ideally other well known packages as well (matplotlib,
 pytables, etc...).
 - if it works for you, or you cannot easily test it, put it for wide
 testing as a basis for the 1.4.0.1 binary
 - if it works, make a RC1 for Numpy 1.4.0.1 (full binaries).

 I think we need to push this ASAP to recover from the current
 confusion w.r.t. binaries.

 That's a sensible plan, I'll start on it right away.

 Just to double-check, can the 1.4.x branch be released as-is? How about the
 version, the version scheme major.minor.micro does not allow for your
 proposed 1.4.0.1. Do you want to just drop the last .1 or make this 1.4.1?


 Patrick, are you okay with David's plan as well? Do you want to do this in
 parallel so we both generate a complete set of binaries?

 Cheers,
 Ralf

 ___
 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
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-24 Thread Patrick Marsh
On Wed, Feb 24, 2010 at 5:19 AM, David Cournapeau da...@silveregg.co.jpwrote:

 Ralf Gommers wrote:
  On Wed, Feb 24, 2010 at 3:42 PM, David Cournapeau courn...@gmail.com
  mailto:courn...@gmail.com wrote:
 
 
  So here is how I see things in the near future for release:
  - compile a simple binary installer for mac os x and windows (no need
  for doc or multiple archs) from 1.4.x
  - test this with the scipy binary out there (running the full test
  suites), ideally other well known packages as well (matplotlib,
  pytables, etc...).
  - if it works for you, or you cannot easily test it, put it for wide
  testing as a basis for the 1.4.0.1 binary
  - if it works, make a RC1 for Numpy 1.4.0.1 (full binaries).
 
  I think we need to push this ASAP to recover from the current
  confusion w.r.t. binaries.
 
  That's a sensible plan, I'll start on it right away.

 Great. Let me know of any glitch.

  Just to double-check, can the 1.4.x branch be released as-is? How about
  the version, the version scheme major.minor.micro does not allow for
  your proposed 1.4.0.1. Do you want to just drop the last .1 or make this
  1.4.1?

 Yes, 1.4.1 is fine. There are a few fixes besides the ABI fix now, so no
 need to complicate things further.

 I think 1.4.x can serve as the basis for 1.4.1 as is. I have not checked
 recently if it builds OK on MS compiler, but not much has changed.



I have the 2008 MSVC compiler already installed and can test  building with
Python 2.6 that this afternoon.  I have an old 2003 MSVC disc that I can use
to install MSVC 7.1 in parallel to allow me to test earlier versions as
well.

Cheers,
Patrick








 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
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-23 Thread David Cournapeau
On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:


 Hi David, did you find time to put those Atlas binaries somewhere?

I am putting them into numpy subversion as we speak (in vendor:
http://svn.scipy.org/svn/numpy/vendor).

cheers,

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-23 Thread josef . pktd
On Tue, Feb 23, 2010 at 8:52 PM, David Cournapeau courn...@gmail.com wrote:
 On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:


 Hi David, did you find time to put those Atlas binaries somewhere?

 I am putting them into numpy subversion as we speak (in vendor:
 http://svn.scipy.org/svn/numpy/vendor).

Thank you,

Are they ok to link to as an update in
 
http://scipy.org/Installing_SciPy/Windows#head-cd37d819e333227e327079e4c2a2298daf625624

the old Atlas is 3.6.0

Josef


 cheers,

 David
 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-23 Thread David Cournapeau
On Wed, Feb 24, 2010 at 11:05 AM,  josef.p...@gmail.com wrote:
 On Tue, Feb 23, 2010 at 8:52 PM, David Cournapeau courn...@gmail.com wrote:
 On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:


 Hi David, did you find time to put those Atlas binaries somewhere?

 I am putting them into numpy subversion as we speak (in vendor:
 http://svn.scipy.org/svn/numpy/vendor).

 Thank you,

 Are they ok to link to as an update in
  http://scipy.org/Installing_SciPy/Windows#head-cd37d819e333227e327079e4c2a2298daf625624

Maybe we should put them also somewhere on the website directly - I am
not sure whether it is good idea to download relatively large binaries
directly from svn.

cheers,

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-23 Thread Ralf Gommers
On Wed, Feb 24, 2010 at 9:52 AM, David Cournapeau courn...@gmail.comwrote:

 On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:
 
 
  Hi David, did you find time to put those Atlas binaries somewhere?

 I am putting them into numpy subversion as we speak (in vendor:
 http://svn.scipy.org/svn/numpy/vendor).

 Thanks a lot!

Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-23 Thread David Cournapeau
On Wed, Feb 24, 2010 at 11:19 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:


 On Wed, Feb 24, 2010 at 9:52 AM, David Cournapeau courn...@gmail.com
 wrote:

 On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:
 
 
  Hi David, did you find time to put those Atlas binaries somewhere?

 I am putting them into numpy subversion as we speak (in vendor:
 http://svn.scipy.org/svn/numpy/vendor).

 Thanks a lot!

So here is how I see things in the near future for release:
- compile a simple binary installer for mac os x and windows (no need
for doc or multiple archs) from 1.4.x
- test this with the scipy binary out there (running the full test
suites), ideally other well known packages as well (matplotlib,
pytables, etc...).
- if it works for you, or you cannot easily test it, put it for wide
testing as a basis for the 1.4.0.1 binary
- if it works, make a RC1 for Numpy 1.4.0.1 (full binaries).

I think we need to push this ASAP to recover from the current
confusion w.r.t. binaries.

cheers,

David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-21 Thread Ralf Gommers
On Tue, Feb 9, 2010 at 9:54 AM, David Cournapeau courn...@gmail.com wrote:

 On Mon, Feb 8, 2010 at 9:14 PM, Ralf Gommers
  Final question is about Atlas and friends. Is 3.8.3 the best version to
  install? Does it compile out of the box under Wine? Is this page
  http://www.scipy.org/Installing_SciPy/Windows still up-to-date with
 regard
  to the Lapack/Atlas info and does it apply for Wine?

 Atlas 3.9.x should not be used, it is too unstable IMO (it is a dev
 version after all, and windows receives little testing compared to
 unix). I will put the Atlas binaries I am using somewhere - building
 Atlas is already painful, but building it with a limited architecture
 on windows takes it to a whole new level (it is not supported by
 atlas, you have to patch the build system by yourself).

 Hi David, did you find time to put those Atlas binaries somewhere?

Thanks,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-09 Thread Ralf Gommers
On Tue, Feb 9, 2010 at 9:54 AM, David Cournapeau courn...@gmail.com wrote:

 On Mon, Feb 8, 2010 at 9:14 PM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:
  Hi David and all,
 
  I have a few questions on setting up the build environment on OS X for
  Windows binaries. I have Wine installed with Python 2.5 and 2.6, MakeNsis
  and MinGW. The first question is what is meant in the Paver script by
 cpuid
  plugin. Wine seems to know what to do with a cpuid instruction, but I
 can
  not find a plugin. Searching for cpuid plugin turns up nothing except
 the
  NumPy pavement.py file. What is this?

 That's a small NSIS plugin to detect at install time the exact
 capabilities of the CPU (SSE2, SSE3, etc...). The sources are found in
 tools/win32build/cpucaps, and should be built with mingw (Visual
 Studio is not supported, it uses gcc-specific inline assembly). You
 then copy the dll into the plugin directory of nsis.


Yep got it. There's quite some stuff hidden in tools/ and vendor/ that I
never noticed before.



  Final question is about Atlas and friends. Is 3.8.3 the best version to
  install? Does it compile out of the box under Wine? Is this page
  http://www.scipy.org/Installing_SciPy/Windows still up-to-date with
 regard
  to the Lapack/Atlas info and does it apply for Wine?

 Atlas 3.9.x should not be used, it is too unstable IMO (it is a dev
 version after all, and windows receives little testing compared to
 unix). I will put the Atlas binaries I am using somewhere


That would be *great*.

Thanks,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-08 Thread josef . pktd
On Mon, Feb 8, 2010 at 7:14 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
 Hi David and all,

 I have a few questions on setting up the build environment on OS X for
 Windows binaries. I have Wine installed with Python 2.5 and 2.6, MakeNsis
 and MinGW. The first question is what is meant in the Paver script by cpuid
 plugin. Wine seems to know what to do with a cpuid instruction, but I can
 not find a plugin. Searching for cpuid plugin turns up nothing except the
 NumPy pavement.py file. What is this?

 Second question is about Fortran. It's needed for SciPy at least, so I may
 as well get it right now. MinGW only comes with g77, and this page:
 http://www.scipy.org/Installing_SciPy/Windows says that this is the default
 compiler. So Fortran 77 on Windows and Fortran 95 on OS X as defaults, is
 that right? No need for g95/gfortran at all?

 Final question is about Atlas and friends. Is 3.8.3 the best version to
 install? Does it compile out of the box under Wine? Is this page
 http://www.scipy.org/Installing_SciPy/Windows still up-to-date with regard
 to the Lapack/Atlas info and does it apply for Wine?  And do I have to
 compile it three times, with the only difference the '-arch' flag set to
 SSE2, SSE3 and what's NoSSE??

Currently scipy binaries are build with MingW 3.4.5, as far as I know,
which includes g77. The latest release of MingW uses gfortran, gcc
4.4.0

I think, that, eventually, scipy should switch to gfortran also on
Windows. But it might need some compatibility testing.
And it would be very useful if someone could provide the Lapack/Atlas
binaries, similar to the ones that are on the scipy webpage for mingw
3.4.5. (I don't have a setup where I can build Atlas binaries).

I haven't switched yet, but, given some comments on the mailinglists,
it looks like several windows users are using gfortran without
reported problems.

Josef






 Thanks,
 Ralf


 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion


___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-08 Thread Ralf Gommers
On Mon, Feb 8, 2010 at 10:25 PM, josef.p...@gmail.com wrote:

 On Mon, Feb 8, 2010 at 7:14 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:
  Hi David and all,
 
  I have a few questions on setting up the build environment on OS X for
  Windows binaries. I have Wine installed with Python 2.5 and 2.6, MakeNsis
  and MinGW. The first question is what is meant in the Paver script by
 cpuid
  plugin. Wine seems to know what to do with a cpuid instruction, but I
 can
  not find a plugin. Searching for cpuid plugin turns up nothing except
 the
  NumPy pavement.py file. What is this?
 
  Second question is about Fortran. It's needed for SciPy at least, so I
 may
  as well get it right now. MinGW only comes with g77, and this page:
  http://www.scipy.org/Installing_SciPy/Windows says that this is the
 default
  compiler. So Fortran 77 on Windows and Fortran 95 on OS X as defaults, is
  that right? No need for g95/gfortran at all?
 
  Final question is about Atlas and friends. Is 3.8.3 the best version to
  install? Does it compile out of the box under Wine? Is this page
  http://www.scipy.org/Installing_SciPy/Windows still up-to-date with
 regard
  to the Lapack/Atlas info and does it apply for Wine?  And do I have to
  compile it three times, with the only difference the '-arch' flag set to
  SSE2, SSE3 and what's NoSSE??

 Currently scipy binaries are build with MingW 3.4.5, as far as I know,
 which includes g77. The latest release of MingW uses gfortran, gcc
 4.4.0


You mean gcc 3.4.5, and yes that's what I've got. MinGW itself is at version
5.1.6 now, and still include gcc and g77 3.4.5. Not sure where you see gcc
4.4.0 but I can easily have missed it on what surely has to be the worst
download page on SourceForge: http://sourceforge.net/projects/mingw/files/


 I think, that, eventually, scipy should switch to gfortran also on
 Windows. But it might need some compatibility testing.
 And it would be very useful if someone could provide the Lapack/Atlas
 binaries, similar to the ones that are on the scipy webpage for mingw
 3.4.5. (I don't have a setup where I can build Atlas binaries).


Where are these binaries hidden? All I can find is
http://scipy.org/Cookbook/CompilingExtensionsOnWindowsWithMinGW



 I haven't switched yet, but, given some comments on the mailinglists,
 it looks like several windows users are using gfortran without
 reported problems.

 Makes sense to use the same Fortran compiler everywhere. gfortran works
well for me on OS X. Thanks Josef.

Cheers,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-08 Thread josef . pktd
On Mon, Feb 8, 2010 at 9:54 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:


 On Mon, Feb 8, 2010 at 10:25 PM, josef.p...@gmail.com wrote:

 On Mon, Feb 8, 2010 at 7:14 AM, Ralf Gommers
 ralf.gomm...@googlemail.com wrote:
  Hi David and all,
 
  I have a few questions on setting up the build environment on OS X for
  Windows binaries. I have Wine installed with Python 2.5 and 2.6,
  MakeNsis
  and MinGW. The first question is what is meant in the Paver script by
  cpuid
  plugin. Wine seems to know what to do with a cpuid instruction, but I
  can
  not find a plugin. Searching for cpuid plugin turns up nothing except
  the
  NumPy pavement.py file. What is this?
 
  Second question is about Fortran. It's needed for SciPy at least, so I
  may
  as well get it right now. MinGW only comes with g77, and this page:
  http://www.scipy.org/Installing_SciPy/Windows says that this is the
  default
  compiler. So Fortran 77 on Windows and Fortran 95 on OS X as defaults,
  is
  that right? No need for g95/gfortran at all?
 
  Final question is about Atlas and friends. Is 3.8.3 the best version to
  install? Does it compile out of the box under Wine? Is this page
  http://www.scipy.org/Installing_SciPy/Windows still up-to-date with
  regard
  to the Lapack/Atlas info and does it apply for Wine?  And do I have to
  compile it three times, with the only difference the '-arch' flag set to
  SSE2, SSE3 and what's NoSSE??

 Currently scipy binaries are build with MingW 3.4.5, as far as I know,
 which includes g77. The latest release of MingW uses gfortran, gcc
 4.4.0

 You mean gcc 3.4.5, and yes that's what I've got. MinGW itself is at version
 5.1.6 now, and still include gcc and g77 3.4.5. Not sure where you see gcc
 4.4.0 but I can easily have missed it on what surely has to be the worst
 download page on SourceForge: http://sourceforge.net/projects/mingw/files/

(I don't think the mingw version is important, it's more important
which gcc is bundled, so I'm sloppy.)

http://sourceforge.net/projects/mingw/files/GCC%20Version%204/Current%20Release_%20gcc-4.4.0/

view all files  and header GCC Version 4

mingw hompage is a bit scarce on information on release version, at
least I don't find it


 I think, that, eventually, scipy should switch to gfortran also on
 Windows. But it might need some compatibility testing.
 And it would be very useful if someone could provide the Lapack/Atlas
 binaries, similar to the ones that are on the scipy webpage for mingw
 3.4.5. (I don't have a setup where I can build Atlas binaries).

 Where are these binaries hidden? All I can find is
 http://scipy.org/Cookbook/CompilingExtensionsOnWindowsWithMinGW

These are the Atlas binaries that I am using with MinGW gcc 3.4.5

http://scipy.org/Installing_SciPy/Windows#head-cd37d819e333227e327079e4c2a2298daf625624



 I haven't switched yet, but, given some comments on the mailinglists,
 it looks like several windows users are using gfortran without
 reported problems.

 Makes sense to use the same Fortran compiler everywhere. gfortran works well
 for me on OS X. Thanks Josef.

 Cheers,
 Ralf


 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion


___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Building Windows binaries on OS X

2010-02-08 Thread Ralf Gommers
On Mon, Feb 8, 2010 at 11:06 PM, josef.p...@gmail.com wrote:

  Currently scipy binaries are build with MingW 3.4.5, as far as I know,
  which includes g77. The latest release of MingW uses gfortran, gcc
  4.4.0
 
  You mean gcc 3.4.5, and yes that's what I've got. MinGW itself is at
 version
  5.1.6 now, and still include gcc and g77 3.4.5. Not sure where you see
 gcc
  4.4.0 but I can easily have missed it on what surely has to be the worst
  download page on SourceForge:
 http://sourceforge.net/projects/mingw/files/


 (I don't think the mingw version is important, it's more important
 which gcc is bundled, so I'm sloppy.)


 http://sourceforge.net/projects/mingw/files/GCC%20Version%204/Current%20Release_%20gcc-4.4.0/

 view all files  and header GCC Version 4


This is not in the current default MinGW bundle, that still pulls in 3.4.5.
But you could indeed install it manually.



 
  I think, that, eventually, scipy should switch to gfortran also on
  Windows. But it might need some compatibility testing.
  And it would be very useful if someone could provide the Lapack/Atlas
  binaries, similar to the ones that are on the scipy webpage for mingw
  3.4.5. (I don't have a setup where I can build Atlas binaries).
 
  Where are these binaries hidden? All I can find is
  http://scipy.org/Cookbook/CompilingExtensionsOnWindowsWithMinGW

 These are the Atlas binaries that I am using with MinGW gcc 3.4.5


 http://scipy.org/Installing_SciPy/Windows#head-cd37d819e333227e327079e4c2a2298daf625624

 Ah yes, thanks. I read that page before, but the word 'Pentium' triggered a
fast-forward.

Cheers,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion