[Numpy-discussion] Problems compiling numeric using python2.4 and VS.Net 2003

[flin at broadpark.no]

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 <stephen.walton at csun.edu>:

> 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 at csun.edu
> 
>