Thanks to all for clearing this up. I have been bouncing this issue off
the folks at Intel and they allege that Intel C++ should be able to do this
independent of the version of VS used originally (I am skeptical). I am still
getting some MKL-related missing symbol errors that we are clearing up and I
will post anything useful that I discover.
~Mike C.
-----Original Message-----
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of David Cournapeau
Sent: Monday, February 02, 2009 7:26 PM
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] f2py: VS version on Windows
On Tue, Feb 3, 2009 at 10:55 AM, Sturla Molden <stu...@molden.no> wrote:
>
>> Python extensions must be built using the same compiler as was used to
>> build the Python binary. Python 2.5.4 was built using MSVC2003 and so
>> extensions for it must be built using the same compiler. The exception
>> to this rule is that extensions built using mingw32 (and msys) will
>> work with most, if not all, windows Python binaries.
>
>
> This is NOT correct.
Although it is technically true, that's relatively irrelevant for
practical matters: it is not currently possible to build numpy with VS
2008 and 7.1 CRT, and you have to build numpy with the same compiler
as the one used by python if you use MS compilers.
David
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
