PETSc configure with Intel-compiler static linking

[Matthew Knepley]

For any configure problem, you MUST send configure.log or we have no idea
what happened.

  Matt

On Thu, Jul 9, 2009 at 2:50 AM, Takuya Sekikawa <sekikawa at msi.co.jp> wrote:

> Hello petsc users,
>
> I need to know how to configure PETSc with Intel-compiler (icc/icpc) on
> static linking.
>
> shared linking is just fine,
> but I need to build PETSc with static-linking. so I tried several
> description.
>
> [1]
> $ ./config/configure.py --with-cc=icc --with-cxx=icpc --with-fc=0
> --with-shared=0 --with-blas-lapack-dir=${MKL_DIR}
>
> environment variable MKL_DIR is set to intel MKL library directory.
> this one is fine, (also compiling and running is ok)
> but is spite of "--with-shared=0" flag, executable still link with .so
> (libmkl_lapack.so, etc)
>
> so I tried another one:
>
> [2]
> $ ./config/configure.py --with-cc=icc --with-cxx=icpc --with-fc=0
> --with-shared=0 --with-blas-lapack-lib=${MKL_DIR}/libmkl_lapack.a
>
> this time configure.py failed:
>
>
> *********************************************************************************
>         UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
>
> ---------------------------------------------------------------------------------------
> You set a value for --with-blas-lapack-lib=<lib>, but
> ['/opt/intel/mkl/10.0.010/lib/em64t/libmkl_lapack.a'] cannot be used
>
> *********************************************************************************
>
> Could someone give me good advice? (or examples are greatly appriciated)
>
> Thanks in advance
>
> Takuya
>



-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20090709/c851dc26/attachment.htm>