[Distutils] pip on windows experience

[Oscar Benjamin]

On 24 January 2014 22:40, Paul Moore <p.f.moore at gmail.com> wrote:
> On 24 January 2014 22:21, Chris Barker <chris.barker at noaa.gov> wrote:
>> well, numpy _should_ build out of the box with nothing special if you are
>> set up to build regular extensions. I understand that a lto f Windows users
>> are not set up to build extensions at all, but tehy ar presumably used to
>> getting "compiler not found" errors (or whatever the message is). But you
>> won't get an optimized numpy and much of the rest of the "stack" is harder
>> to build: scipy, matplotlib.
>
> Seriously? If I have MSVC 2010 installed, pip install numpy will
> correctly build numpy from source? It's a *long* time since I tried
> this, but I really thought building numpy was harder than that.
>
> A quick test later:
> No BLAS/ATLAS/LAPACK causes a string of warnings, And ignoring the
> rest of the error stack (which I'm frankly not interested in investing
> the time to diagnose and fix) I get "RuntimeError: Broken toolchain:
> cannot link a simple C program". Which is utter rubbish - I routinely
> build extensions with this installation.
>
> So no, numpy does not build out of the box. Ah well.

Last time I tried with mingw it worked (I've since departed the
Windows world). I think official numpy binaries for Windows are built
with mingw (Christoph uses MSVC though).


Oscar