Re:

["Matthew Knepley" <knepley@xxxxxxxxx>]

If you want shared libraries, you need to use --with-shared and the tests
have to pass. This kind of question belongs on petsc-maint@xxxxxxxxxxxx

 Thanks,

   Matt

On 3/26/07, SLIM H.A. <h.a.slim@xxxxxxxxxxxx> wrote:
> Dear Satish
>
> This worked now.
>
> ./config/configure.py
> --with-blas-lapack-lib=\[/usr/local/Cluster-Apps/intel/mkl/8.0/lib/em64t
> /libmkl_lapack64.so,libmkl_def.so,libguide.so\]
> --with-vendor-compilers=intel --with-gnu-compilers=0
>
> The tests were succesfull with up to two mpi processes. However when I
> look into the lib directory there are only static libraries:
> hamilton_dcl0has(296)>ls -la  lib/linux-gnu-intel
> total 27248
> drwx------  2 dcl0has dcl     4096 Mar 26 17:39 ./
> drwx------  4 dcl0has dcl     4096 Mar 23 16:43 ../
> -rw-------  1 dcl0has dcl  4394974 Mar 26 17:39 libpetsc.a
> -rw-------  1 dcl0has dcl   193378 Mar 26 17:39 libpetsccontrib.a
> -rw-------  1 dcl0has dcl  2612462 Mar 26 17:39 libpetscdm.a
> -rw-------  1 dcl0has dcl  4525610 Mar 26 17:39 libpetscksp.a
> -rw-------  1 dcl0has dcl 10905628 Mar 26 17:39 libpetscmat.a
> -rw-------  1 dcl0has dcl  1476668 Mar 26 17:39 libpetscsnes.a
> -rw-------  1 dcl0has dcl   685944 Mar 26 17:39 libpetscts.a
> -rw-------  1 dcl0has dcl  3025700 Mar 26 17:39 libpetscvec.a
>
> Regards
>
> henk
>
>
> > -----Original Message-----
> > From: owner-petsc-users@xxxxxxxxxxx
> > [mailto:owner-petsc-users@xxxxxxxxxxx] On Behalf Of Satish Balay
> > Sent: 26 March 2007 17:14
> > To: petsc-users@xxxxxxxxxxx
> > Subject: RE:
> >
> > With tcsh shell - one has to escape the special chars. [with
> > bash the command should work as is].
> >
> > i.e
> >
> > --with-blas-lapack-lib=\[/usr/local/Cluster-Apps/intel/mkl/8.0
> > /lib/em64t/libmkl_lapack64.so\,libmkl_def.so\,libguide.so\]
> >
> > Satish
> >
> >
> > On Mon, 26 Mar 2007, SLIM H.A. wrote:
> >
> > > Thanks
> > >
> > > I tried
> > > ./config/configure.py
> > >
> > --with-blas-lapack-lib=[/usr/local/Cluster-Apps/intel/mkl/8.0/lib/em64
> > > t/ libmkl_lapack64.so,libmkl_def.so,libguide.so]
> > > --with-vendor-compilers=intel --with-gnu-compilers=0
> > >
> > > which gives:
> > > ./config/configure.py: No match.
> > >
> > > I checked that the files
> > libmkl_lapack64.so,libmkl_def.so,libguide.so
> > > exist in /usr/local/Cluster-Apps/intel/mkl/8.0/lib/em64t
> > >
> > > However I am not familiar with the configure command. Did I use it
> > > corrctly?
> > >
> > > Thanks
> > > Henk
> > >
> > >
> > > > -----Original Message-----
> > > > From: owner-petsc-users@xxxxxxxxxxx
> > > > [mailto:owner-petsc-users@xxxxxxxxxxx] On Behalf Of Satish Balay
> > > > Sent: 26 March 2007 16:28
> > > > To: petsc-users@xxxxxxxxxxx
> > > > Subject: Re:
> > > >
> > > > Not sure about the binutils stuff - but x86_64 linux
> > complains about
> > > > using non PIC code in a shared library.
> > > >
> > > > Currently PETSc configure is defaulting to .a version of MKL
> > > > - which are incompatible with sharedlibraries.  And I'm not sure
> > > > what the correct library naems are for the shared version
> > of MLK.
> > > > You could try using the option:
> > > >
> > > > --with-blas-lapack-lib=[/usr/local/Cluster-Apps/intel/mkl/8.0/
> > > lib/em64t/libmkl_lapack32.so,libmkl_def.so,libguide.so]
> > > >
> > > > or just use --download-f-blas-lapack=1
> > > >
> > > > Satish
> > > >
> > > > On Mon, 26 Mar 2007, Lisandro Dalcin wrote:
> > > >
> > > > > This seems to be a bug of 'binutils' in 64 bits machines.
> > > > >
> > > > > http://sources.redhat.com/bugzilla/show_bug.cgi?id=584
> > > > >
> > > > > but apparently it was fixed in Feb 2005
> > > > >
> > > > > http://sourceware.org/ml/binutils-cvs/2005-02/msg00011.html
> > > > >
> > > > > Can you upgrade your 'binutils' package and try what happens?
> > > > >
> > > > >
> > > > > On 3/26/07, SLIM H.A. <h.a.slim@xxxxxxxxxxxx> wrote:
> > > > > > Dear users
> > > > > >
> > > > > > I want to build petsc with shared object libraries but get
> > > > > > errors when building libpetscmat.so and libpetscksp.so I am
> > > > using the intel
> > > > > > compiler and intel's imkl for lapack/blas
> > > > > >
> > > > > > Configuration is:
> > > > > > ./config/configure.py
> > > > > >
> > > >
> > --with-blas-lapack-dir=/usr/local/Cluster-Apps/intel/mkl/8.0/lib/em6
> > > > > > 4t --with-vendor-compilers=intel --with-gnu-compilers=0
> > > > > > --with-shared
> > > > > >
> > > > > > The error is:
> > > > > > ld:
> > > > > >
> > > >
> > /usr/local/Cluster-Apps/intel/mkl/8.0/lib/em64t/libmkl_lapack.a(dget
> > > > > > rf_o
> > > > > > mp.o): relocation R_X86_64_PC32 against
> > > > > > `_mkl_lapack_dgetrf_omp_271__par_loop0' can not be used
> > > > when making
> > > > > > a shared object; recompile with -fPIC
> > > > > > ld: final link failed: Bad value
> > > > > > make[2]: [shared_linux] Error 1 (ignored)
> > > > > >
> > > > > > Details are in the attached male log file.
> > > > > >
> > > > > > Thanks for any help
> > > > > >
> > > > > > Henk
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >


--
One trouble is that despite this system, anyone who reads journals widely
and critically is forced to realize that there are scarcely any bars to eventual
publication. There seems to be no study too fragmented, no hypothesis too
trivial, no literature citation too biased or too egotistical, no design too
warped, no methodology too bungled, no presentation of results too
inaccurate, too obscure, and too contradictory, no analysis too self-serving,
no argument too circular, no conclusions too trifling or too unjustified, and
no grammar and syntax too offensive for a paper to end up in print. --
Drummond Rennie