Thanks. I've added the installation details and output from a test run. Paul On 30 January 2014 10:25, David Cournapeau <cournape@gmail.com> wrote:
On Thu, Jan 30, 2014 at 10:20 AM, Paul Moore <p.f.moore@gmail.com> wrote:
On 30 January 2014 09:12, David Cournapeau <cournape@gmail.com> wrote:
On Thu, Jan 30, 2014 at 7:50 AM, Paul Moore <p.f.moore@gmail.com> wrote:
On 29 January 2014 22:50, David Cournapeau <cournape@gmail.com> wrote:
i.e. it would be nice if anyone setup to build C extensions could "just build numpy".
This has always been possible, and if not, that's certainly considered as a bug (I would be eager to fix).
I don't know if you saw my comment earlier in this thread:
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.
This is a straight "pip install numpy" run in a virtualenv on Windows 7 64-bit with MSVC 2010 (full edition) installed.
which version of python ?
For 2.x, it is expected to fail at that point, since you can't build C extensions with something different than 2008 (with python.org builds).
For 3.3, it means there is a bug that needs to be fixed.
Doh. Sorry, I knew I'd forget something. 3.3.
Here we go: https://github.com/numpy/numpy/issues/4245
David
Paul