Re: [Numpy-discussion] F2PY errors still exist (possible solution)
To All, I can now see as to where the error lies. I apologize for my poor eye sight. The error lies in me using Compaq Visual Fortran 6.0. The error listed from f2py.py after I enter the following commands are the following: Commands Entered >>> C:\Python25\Scripts>C:\python25\python f2py.py -c --fcompiler=compaqv -m hello hello.f90 Error obtained >>> LINK: fatal error LNK1104: cannot open file "dformd.lib" Possible Solution >>> This error results from the Compaq Visual Fortran compiler not being installed with the proper file folder arrangement. The recommended file arrangement for the Compaq Visual Fortran compiler is as follows: Developer Studio Files: C:\Program Files\Microsoft Visual Studio\Common Visual Fortran Files: C:\Program Files\Microsoft Visual Studio\Df98 Shared Visual C++ Files: C:\Program Files\Microsoft Visual Studio\VC98 Should I just uninstall and then reinstall Compaq Visual Fortran 6.) to resolve this issue? Thanks, David Blubaugh -Original Message- From: Blubaugh, David A. Sent: Thursday, September 25, 2008 5:44 PM To: 'numpy-discussion@scipy.org' Subject: F2PY errors still exist To All, I am now trying to use the visual compaq compiler. I am legally required to utilize this compiler for my employment. I have tried the following: C:\Python25\Scripts>C:\python25\python f2py.py -c --fcompiler=compaqv -m hello hello.f90 I was wondering as to if I should input --compiler=msvc. If so, I am also obtaining an error with that as well. I will then obtain the following error!! I am now starting to becomed deeply concerned about F2PY's inability to generate any working executable or DLL files in capacity. The errors are as follows: running build running scons No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler Found executable C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.e xe customize GnuFCompiler Could not locate executable g77 Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f77.exe gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f77.exe customize IntelVisualFCompiler Could not locate executable ifl customize AbsoftFCompiler Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f90.exe Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f90.exe customize CompaqVisualFCompiler Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\DF.exe Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\DF.exe customize CompaqVisualFCompiler No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler Missing compiler_cxx fix for MSVCCompiler customize MSVCCompiler using scons 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\david\locals~1\temp\tmpmladol\src.win32-2.5\hellomodule.c creating c:\docume~1\david\locals~1\temp\tmpmladol creating c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5 Reading fortran codes... Reading file 'hello.f90' (format:free) 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\david\locals~1\temp\tmpm ladol\src.win32-2.5/hellomodule.c" adding 'c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5\fortranobject. c' to sources. adding 'c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5' to include_di rs. copying C:\python25\lib\site-packages\numpy\f2py\src\fortranobject.c -> c:\docum e~1\david\locals~1\temp\tmpmladol\src.win32-2.5 copying C:\python25\lib\site-packages\numpy\f2py\src\fortranobject.h -> c:\docum e~1\david\locals~1\temp\tmpmladol\src.win32-2.5 running build_ext No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler customize MSVCCompiler using build_ext customize CompaqVisualFCompiler customize CompaqVisualFCompiler using build_ext building 'hello' extension compiling C sources creating c:\docume~1\david\locals~1\temp\tmpmladol\Release creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1 creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1 creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1\temp creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1\temp\tmpmladol creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docum
[Numpy-discussion] F2PY errors still exist
To All, I am now trying to use the visual compaq compiler. I am legally required to utilize this compiler for my employment. I have tried the following: C:\Python25\Scripts>C:\python25\python f2py.py -c --fcompiler=compaqv -m hello hello.f90 I was wondering as to if I should input --compiler=msvc. If so, I am also obtaining an error with that as well. I will then obtain the following error!! I am now starting to becomed deeply concerned about F2PY's inability to generate any working executable or DLL files in capacity. The errors are as follows: running build running scons No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler Found executable C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.e xe customize GnuFCompiler Could not locate executable g77 Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f77.exe gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f77.exe customize IntelVisualFCompiler Could not locate executable ifl customize AbsoftFCompiler Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f90.exe Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\f90.exe customize CompaqVisualFCompiler Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\DF.exe Found executable C:\Program Files\Microsoft Visual Studio\DF98\BIN\DF.exe customize CompaqVisualFCompiler No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler Missing compiler_cxx fix for MSVCCompiler customize MSVCCompiler using scons 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\david\locals~1\temp\tmpmladol\src.win32-2.5\hellomodule.c creating c:\docume~1\david\locals~1\temp\tmpmladol creating c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5 Reading fortran codes... Reading file 'hello.f90' (format:free) 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\david\locals~1\temp\tmpm ladol\src.win32-2.5/hellomodule.c" adding 'c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5\fortranobject. c' to sources. adding 'c:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5' to include_di rs. copying C:\python25\lib\site-packages\numpy\f2py\src\fortranobject.c -> c:\docum e~1\david\locals~1\temp\tmpmladol\src.win32-2.5 copying C:\python25\lib\site-packages\numpy\f2py\src\fortranobject.h -> c:\docum e~1\david\locals~1\temp\tmpmladol\src.win32-2.5 running build_ext No module named msvccompiler in numpy.distutils; trying from distutils customize MSVCCompiler customize MSVCCompiler using build_ext customize CompaqVisualFCompiler customize CompaqVisualFCompiler using build_ext building 'hello' extension compiling C sources creating c:\docume~1\david\locals~1\temp\tmpmladol\Release creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1 creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1 creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1\temp creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1\temp\tmpmladol creating c:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\locals ~1\temp\tmpmladol\src.win32-2.5 C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe /c /nologo /Ox /MD /W3 /GX /DNDEBUG -Ic:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5 -IC:\python25\lib\site-packages\numpy\core\include -IC:\python25\include -IC:\py thon25\PC /Tcc:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5\hellomodule .c /Foc:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\loca ls~1\ temp\tmpmladol\src.win32-2.5\hellomodule.obj Found executable C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.e xe C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe /c /nologo /Ox /MD /W3 /GX /DNDEBUG -Ic:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5 -IC:\python25\lib\site-packages\numpy\core\include -IC:\python25\include -IC:\py thon25\PC /Tcc:\docume~1\david\locals~1\temp\tmpmladol\src.win32-2.5\fortranobje ct.c /Foc:\docume~1\david\locals~1\temp\tmpmladol\Release\docume~1\david\loca ls~ 1\temp\tmpmladol\src.win32-2.5\fortranobject.obj compiling Fortran sources Fortran f77 compiler: C:\Program Files\Microsoft Visual Studio\DF98\BIN\DF.exe / f77rtl /fixed /nologo /MD /WX /if
Re: [Numpy-discussion] F2py errors still
On Fri, Sep 12, 2008 at 12:34 PM, Blubaugh, David A. <[EMAIL PROTECTED]> wrote: > In response to your statement I cannot find Numpy 1.2 listed. Where is > it??? I haven't announced rc2 yet, since I am still waiting to get the binaries built (should be out later today). But since you are building yourself, here are the links: The 1.2.0rc2 svn tag: http://svn.scipy.org/svn/numpy/tags/1.2.0rc2 The source tarball: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc2.tar.gz -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2py errors still
Robert, In response to your statement I cannot find Numpy 1.2 listed. Where is it??? David Blubaugh > I believe this got fixed recently. Please try the latest release candidate of numpy 1.2. > And please try to stay in one mailing list thread. This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2py errors still
On Thu, Sep 11, 2008 at 16:42, Blubaugh, David A. <[EMAIL PROTECTED]> wrote: > To All, > > I am still not sure as to why this is not working. I believe it could > be my windows environment variables. However, I have set these > variables based on the following webpage: > > > http://www.scipy.org/F2PY_Windows > > > The error that I obtain is the following: > > > C:\python25\python C:\python25\scripts\f2py.py -c --fcomplier=gnu95 > --compiler=mingw32 -m foo foo.f90 > > running build > running scons > 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. > > Why that I need to have Visual Studio 2003 is beyond me. Does anyone > have any suggestions. I believe this got fixed recently. Please try the latest release candidate of numpy 1.2. And please try to stay in one mailing list thread. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] F2py errors still
To All, I am still not sure as to why this is not working. I believe it could be my windows environment variables. However, I have set these variables based on the following webpage: http://www.scipy.org/F2PY_Windows The error that I obtain is the following: C:\python25\python C:\python25\scripts\f2py.py -c --fcomplier=gnu95 --compiler=mingw32 -m foo foo.f90 running build running scons 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. Why that I need to have Visual Studio 2003 is beyond me. Does anyone have any suggestions. David Blubaugh This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
