Problems compiling numeric using python2.4 and VS.Net 2003
Hi, I need numeric in a python2.4 / win32 project. Is there a binary installer somewhere? I tried to compile it from source but ran into the following problem (se below): Where are the libs supposed to come from? - Frank C:\users\frankl\download\Numeric-23.5>c:\Python24\python.exe setup.py install running install running build running build_py running build_ext building 'lapack_lite' extension C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\link.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:/usr/lib/atlas /LIBPATH:c:\Python24\libs /LIBPATH:c:\P ython24\PCBuild lapack.lib cblas.lib f77blas.lib atlas.lib g2c.lib /EXPORT:initl apack_lite build\temp.win32-2.4\Release\Src\lapack_litemodule.obj /OUT:build\lib .win32-2.4\lapack_lite.pyd /IMPLIB:build\temp.win32-2.4\Release\Src\lapack_lite. lib LINK : fatal error LNK1181: cannot open input file 'lapack.lib' error: command '"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\link .exe"' failed with exit status 1181 C:\users\frankl\download\Numeric-23.5>
On Wed, 2004-10-20 at 11:17 +0200, Frank Lindseth wrote:
LINK : fatal error LNK1181: cannot open input file 'lapack.lib'
Edit setup.py, setting the variables library_dirs_list and libraries_list to empty lists, and try again. List: shouldn't this be the default? Right now Numeric looks for ATLAS by default. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge stephen.walton@csun.edu
Thank you for the replay Stephen,
I did as you suggested:
library_dirs_list = []
libraries_list = []
#library_dirs_list = ['/usr/lib/atlas']
#libraries_list = ['lapack', 'cblas', 'f77blas', 'atlas', 'g2c']
but it still woun't install (se below)
Any suggestions?
C:\users\frankl\download\Numeric-23.5>c:\Python24\python.exe setup.py install
running install
running build
running build_py
running build_ext
building 'lapack_lite' extension
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\link.exe /DLL
/nologo
/INCREMENTAL:NO /LIBPATH:c:\Python24\libs /LIBPATH:c:\Python24\PCBuild
/EXPORT:
initlapack_lite build\temp.win32-2.4\Release\Src\lapack_litemodule.obj
/OUT:buil
d\lib.win32-2.4\lapack_lite.pyd
/IMPLIB:build\temp.win32-2.4\Release\Src\lapack_
lite.lib
Creating library build\temp.win32-2.4\Release\Src\lapack_lite.lib and object
build\temp.win32-2.4\Release\Src\lapack_lite.exp
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dgeev_
refere
nced in function _lapack_lite_dgeev
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dsyevd_
refer
enced in function _lapack_lite_dsyevd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zheevd_
refer
enced in function _lapack_lite_zheevd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dgelsd_
refer
enced in function _lapack_lite_dgelsd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dgesv_
refere
nced in function _lapack_lite_dgesv
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dgesdd_
refer
enced in function _lapack_lite_dgesdd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dgetrf_
refer
enced in function _lapack_lite_dgetrf
lapack_litemodule.obj : error LNK2019: unresolved external symbol _dpotrf_
refer
enced in function _lapack_lite_dpotrf
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zgeev_
refere
nced in function _lapack_lite_zgeev
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zgelsd_
refer
enced in function _lapack_lite_zgelsd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zgesv_
refere
nced in function _lapack_lite_zgesv
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zgesdd_
refer
enced in function _lapack_lite_zgesdd
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zgetrf_
refer
enced in function _lapack_lite_zgetrf
lapack_litemodule.obj : error LNK2019: unresolved external symbol _zpotrf_
refer
enced in function _lapack_lite_zpotrf
build\lib.win32-2.4\lapack_lite.pyd : fatal error LNK1120: 14 unresolved
externa
ls
error: command '"C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\bin\link
.exe"' failed with exit status 1120
C:\users\frankl\download\Numeric-23.5>
Quoting Stephen Walton
On Wed, 2004-10-20 at 11:17 +0200, Frank Lindseth wrote:
LINK : fatal error LNK1181: cannot open input file 'lapack.lib'
Edit setup.py, setting the variables library_dirs_list and libraries_list to empty lists, and try again.
List: shouldn't this be the default? Right now Numeric looks for ATLAS by default.
-- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge stephen.walton@csun.edu
On Wed, 2004-10-20 at 20:40 +0200, flin@broadpark.no wrote:
Thank you for the replay Stephen, I did as you suggested: library_dirs_list = [] libraries_list = [] #library_dirs_list = ['/usr/lib/atlas'] #libraries_list = ['lapack', 'cblas', 'f77blas', 'atlas', 'g2c']
but it still woun't install (se below) Any suggestions?
I'm guessing you still have files left over from last time. On Unix, you can run the 'makeclean.sh' script. On Windows, manually deleting the directories listed in that script (they are all called build) should do the trick. Then try the 'setup.py build' again. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge stephen.walton@csun.edu
Thanks again Stephen.
Still no success.
I deleted the whole Numeric-directory-tree,
unzipped a newly downloaded src-file,
edited the setup.py as you suggested,
tried to run the installer,
same error.
I'm not sure what to du next?
(what canm't somebody just make a binary installer for python2.4,
after all it's in beta now...)
- Frank
--------
Quoting Stephen Walton
On Wed, 2004-10-20 at 20:40 +0200, flin@broadpark.no wrote:
Thank you for the replay Stephen, I did as you suggested: library_dirs_list = [] libraries_list = [] #library_dirs_list = ['/usr/lib/atlas'] #libraries_list = ['lapack', 'cblas', 'f77blas', 'atlas', 'g2c']
but it still woun't install (se below) Any suggestions?
I'm guessing you still have files left over from last time. On Unix, you can run the 'makeclean.sh' script. On Windows, manually deleting the directories listed in that script (they are all called build) should do the trick. Then try the 'setup.py build' again.
-- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge stephen.walton@csun.edu
On Wed, 2004-10-20 at 15:56, flin@broadpark.no wrote:
Thanks again Stephen. Still no success.
Sorry. Being a Linux user I'm afraid I can't help much.
I'm not sure what to du next?
Download SciPy from http://www.scipy.org/? It is much more than you
actually need, being all of Scientific Python as well as Numeric, but at
least it's an all-in-one installer.
--
Stephen Walton
flin@broadpark.no wrote:
Thanks again Stephen. Still no success. I deleted the whole Numeric-directory-tree, unzipped a newly downloaded src-file, edited the setup.py as you suggested, tried to run the installer, same error.
Previously I managed to compile Numeric for Python 2.4 on Windows, using the MinGW compiler and Atlas. If you still need it, I can send you the binaries.
I'm not sure what to du next? (what canm't somebody just make a binary installer for python2.4, after all it's in beta now...)
There is a bug in Python 2.4 that prevents users from running bdist_wininst to create a binary installer. python setup.py install fails too. See bug 1021756 on sourceforge. --Michiel, U Tokyo. -- Michiel de Hoon, Assistant Professor University of Tokyo, Institute of Medical Science Human Genome Center 4-6-1 Shirokane-dai, Minato-ku Tokyo 108-8639 Japan http://bonsai.ims.u-tokyo.ac.jp/~mdehoon
participants (4)
-
flin@broadpark.no
-
Frank Lindseth
-
Michiel Jan Laurens de Hoon
-
Stephen Walton