[petsc-users] Calling convention from windows VC++ and IFC

[Satish Balay]

can you send the corresponding configure.log and make.log to petsc-maint at mcs.anl.gov?

Satish

On Thu, 3 Mar 2011, Alexander Grayver wrote:

> Hello,
> 
> I built PETSc-3.1 using VC++ 2008 and IFC 10.1 with the following
> configuration line:
> 
> ./config/configure.py --with-cc='win32fe cl' --with-fc='win32fe ifort'
> --with-cxx='win32fe cl'  --download-f-blas-lapack=1 --with-precision=double
> --with-scalar-type=complex --with-clanguage=cxx
> --with-mpi-include="/cygdrive/d/Dev/HPC_2008_SDK/Include"
> --with-mpi-lib=["/cygdrive/d/Dev/HPC_2008_SDK/Lib/amd64/msmpi.lib","/cygdrive/d/Dev/HPC_2008_SDK/Lib/amd64/msmpifec.lib"]
> --useThreads=0 --with-shared=0
> 
> Note there is C++ as main language.
> 
> Now, when I'm trying to build examples I always get similar errors:
> 
> Error    2     error LNK2019: unresolved external symbol ZGESVD referenced in
> function "int __cdecl KSPComputeExtremeSingularValues_GMRES(struct _p_KSP
> *,double *,double *)"
> (?KSPComputeExtremeSingularValues_GMRES@@YAHPEAU_p_KSP@@PEAN1 at Z)
> libpetsc.lib
> Error    3     error LNK2019: unresolved external symbol ZGEEV referenced in
> function "int __cdecl KSPComputeEigenvalues_GMRES(struct _p_KSP *,int,double
> *,double *,int *)" (?KSPComputeEigenvalues_GMRES@@YAHPEAU_p_KSP@@HPEAN1PEAH at Z)
> libpetsc.lib
> Error    4     error LNK2001: unresolved external symbol ZGEEV    libpetsc.lib
> Error    5     error LNK2019: unresolved external symbol DZNRM2 referenced in
> function "int __cdecl VecNorm_MPI(struct _p_Vec *,enum NormType,double *)"
> (?VecNorm_MPI@@YAHPEAU_p_Vec@@W4NormType@@PEAN at Z)    libpetsc.lib
> Error    6     error LNK2001: unresolved external symbol DZNRM2
> libpetsc.lib
> Error    7     error LNK2019: unresolved external symbol DZASUM referenced in
> function "int __cdecl VecNorm_Seq(struct _p_Vec *,enum NormType,double *)"
> (?VecNorm_Seq@@YAHPEAU_p_Vec@@W4NormType@@PEAN at Z)    libpetsc.lib
> ...
> 
> It look like calling conventions are in disagreement. Any ideas? May be I
> should specify conventions myself in configuration line? If so, how to do
> that?
>