[petsc-users] Problem with linking PETSc
Satish Balay
balay at mcs.anl.gov
Thu Aug 27 10:38:59 CDT 2015
Are you able to compile and run both C and fortran petsc examples
using the corresponding makefile?
Satish
On Thu, 27 Aug 2015, TAY wee-beng wrote:
> Hi,
>
> I used to compile and link using PETSc 3.6.0 + MPICH2 on VS2008.
>
> Due to some MPICH2 issues, I am trying to use Intel MPI (newest version).
> Building and testing of PETSc 3.6.1 with Intel MPI all went smoothly.
>
> However, I now have problem linking the files on VS2008 to create the final
> exe. The error is:
>
> /*1>Compiling manifest to resources...*//*
> *//*1>Microsoft (R) Windows (R) Resource Compiler Version 6.0.5724.0*//*
> *//*1>Copyright (C) Microsoft Corporation. All rights reserved.*//*
> *//*1>Linking...*//*
> *//*1>global.obj : error LNK2019: unresolved external symbol MATCREATEAIJ
> referenced in function GLOBAL_DATA_mp_ALLO_VAR*//*
> *//*1>global.obj : error LNK2019: unresolved external symbol MATSETFROMOPTIONS
> referenced in function GLOBAL_DATA_mp_ALLO_VAR*//*
> *//*...*//*
> *//*1>PETSc_solvers.obj : error LNK2019: unresolved external symbol
> VECGETARRAY referenced in function PETSC_SOLVERS_mp_P_MATRIX_SOLV_PETSC*//*
> *//*1>PETSc_solvers.obj : error LNK2019: unresolved external symbol
> VECRESTOREARRAY referenced in function
> PETSC_SOLVERS_mp_P_MATRIX_SOLV_PETSC*//*
> *//*1>PETSc_solvers.obj : error LNK2019: unresolved external symbol
> DMLOCALTOLOCALBEGIN referenced in function
> PETSC_SOLVERS_mp_DM_UPDATE_ARRAY*//*
> *//*1>PETSc_solvers.obj : error LNK2019: unresolved external symbol
> DMLOCALTOLOCALEND referenced in function PETSC_SOLVERS_mp_DM_UPDATE_ARRAY*//*
> *//*1>ibm3d_high_Re.obj : error LNK2019: unresolved external symbol
> PETSCINITIALIZE referenced in function MAIN__*//*
> *//*1>C:\Obj_tmp\ibm3d_IIB_mpi_old\Debug\ibm3d_IIB_mpi.exe : fatal error
> LNK1120: 74 unresolved externals*//*
> *//*1>*//*
> *//*1>Build log written to
> "file://C:\Obj_tmp\ibm3d_IIB_mpi_old\Debug\BuildLog.htm"*//*
> *//*1>ibm3d_IIB_mpi_old - 165 error(s), 0 warning(s)*//*
> *//*========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========*/
>
> I did not do much changes since the prev PETSc worked. I only changed the
> directory $(PETSC_DIR) and $(IMPI) to the new directory in win7 environment
> variables. I wonder what's wrong.
>
>
More information about the petsc-users
mailing list