[Numpy-discussion] f2py: VS version on Windows

Patrick Marsh patrickmarshwx@gmail....
Mon Feb 2 18:01:51 CST 2009


Hi Mike,

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.

-Patrick






On Mon, Feb 2, 2009 at 5:56 PM, Mike Colonno <Mike.Colonno@spacex.com> wrote:
>             I'm trying to test out f2py in Windows (python 2.5.4 32-bit for
> now + most recent Numpy). I'd like to use the Intel compilers, but msvc is
> fine if needed. I get the output below about which I have a question re: the
> warning about VS version. I have VS 2008 currently which should have no
> trouble making binaries compatible with older version of VS(?) Is there any
> way around this error with VS > 2003?
>
>
>
>             Thanks,
>
>             ~Mike C.
>
>
>
>
>
> C:\Python25\Lib\site-packages\numpy\f2py\docs>C:\Python25\Scripts\f2py.py -c
> --f
>
> compiler=intel -m hello hello.f
>
> Ignoring "Python was built with Visual Studio 2003;
>
> extensions must be built with a compiler than can generate compatible
> binaries.
>
> Visual Studio 2003 was not found on this system. If you have Cygwin
> installed,
>
> you can try compiling with MingW32, by passing "-c mingw32" to setup.py."
> (one s
>
> hould fix me in fcompiler/compaq.py)
>
> running build
>
> running config_cc
>
> unifing config_cc, config, build_clib, build_ext, build commands --compiler
> opti
>
> ons
>
> running config_fc
>
> unifing config_fc, config, build_clib, build_ext, build commands --fcompiler
> opt
>
> ions
>
> running build_src
>
> building extension "hello" sources
>
> f2py options: []
>
> f2py:> c:\docume~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5\hellomodule.c
>
> creating c:\docume~1\mike\locals~1\temp\tmptd0t5g
>
> creating c:\docume~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5
>
> Reading fortran codes...
>
>         Reading file 'hello.f' (format:fix,strict)
>
> Post-processing...
>
>         Block: hello
>
>                         Block: foo
>
> Post-processing (stage 2)...
>
> Building modules...
>
>         Building module "hello"...
>
>                 Constructing wrapper function "foo"...
>
>                   foo(a)
>
>         Wrote C/API module "hello" to file
> "c:\docume~1\mike\locals~1\temp\tmptd
>
> 0t5g\src.win32-2.5/hellomodule.c"
>
>   adding
> 'c:\docume~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5\fortranobject.c
>
> ' to sources.
>
>   adding 'c:\docume~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5' to
> include_dir
>
> s.
>
> copying C:\Python25\lib\site-packages\numpy\f2py\src\fortranobject.c ->
> c:\docum
>
> e~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5
>
> copying C:\Python25\lib\site-packages\numpy\f2py\src\fortranobject.h ->
> c:\docum
>
> e~1\mike\locals~1\temp\tmptd0t5g\src.win32-2.5
>
> running build_ext
>
> No module named msvccompiler in numpy.distutils; trying from distutils
>
> error: Python was built with Visual Studio 2003;
>
> extensions must be built with a compiler than can generate compatible
> binaries.
>
> Visual Studio 2003 was not found on this system. If you have Cygwin
> installed,
>
> you can try compiling with MingW32, by passing "-c mingw32" to setup.py.
>
>
>
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion@scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>
>



-- 
Patrick Marsh
Graduate Research Assistant
School of Meteorology
University of Oklahoma
http://www.patricktmarsh.com


More information about the Numpy-discussion mailing list