Re: [petsc-users] Could not determine how to create a shared library!

[Zhang, Hong]

The MKL version you are trying to use does not match the environment setting on 
Theta.

hongzh@thetalogin6:~/Projects/petsc (master)$ module list
Currently Loaded Modulefiles:
  1) modules/3.2.10.6  10) 
dmapp/7.1.1-6.0.4.0_46.2__gb8abda2.ari19) PrgEnv-intel/6.0.4
  2) eproxy/2.0.16-6.0.4.1_3.1__g001b199.ari   11) 
gni-headers/5.0.11-6.0.4.0_7.2__g7136988.ari  20) craype-mic-knl
  3) intel/18.0.0.128  12) 
xpmem/2.2.2-6.0.4.1_18.2__g43b0535.ari21) cray-mpich/7.7.0
  4) craype-network-aries  13) 
job/2.2.2-6.0.4.0_8.2__g3c644b5.ari   22) nompirun/nompirun
  5) craype/2.5.14 14) 
dvs/2.7_2.2.36-6.0.4.1_16.2__g4c8274a 23) darshan/3.1.5
  6) cray-libsci/18.04.1   15) 
alps/6.4.2-6.0.4.1_3.1__gb8adc61.ari  24) trackdeps
  7) udreg/2.3.2-6.0.4.0_12.2__g2f9c3ee.ari16) 
rca/2.2.15-6.0.4.1_13.1__g46acb0f.ari 25) xalt
  8) ugni/6.0.14-6.0.4.0_14.1__ge7db4a2.ari17) atp/2.1.1
 26) cray-hdf5-parallel/1.10.1.1
  9) pmi/5.0.1318) perftools-base/7.0.1

By default, 18.0.0.128 is loaded. Your petsc configuration should work with 
18.0.2.199 if you do

module swap intel/18.0.0.128 intel/18.0.2.199

Hong (Mr.)

On May 3, 2018, at 11:00 AM, Kong, Fande 
> wrote:

Thanks,

I get the PETSc complied, but theta does not like the shared lib, I think.

I am switching back to a static lib.   I ever successfully built and ran the 
PETSc with the static compiling.

But I encountered a problem this time on building blaslapack.


Thanks,

Fande

On Tue, May 1, 2018 at 2:22 PM, Satish Balay 
> wrote:
This is theta..

Try: using --LDFLAGS=-dynamic option

[as listed in config/examples/arch-cray-xc40-knl-opt.py]

Satish

On Tue, 1 May 2018, Kong, Fande wrote:

> Hi All,
>
> I can build a static petsc library on a supercomputer, but could not do the
> same thing with " --with-shared-libraries=1".
>
> The log file is attached.
>
>
> Fande,
>

Re: [petsc-users] Could not determine how to create a shared library!

[Kong, Fande]

On Thu, May 3, 2018 at 11:50 AM, Zhang, Hong  wrote:

> Alternatively you can use --with-blaslapack-dir=/opt/
> intel/compilers_and_libraries/linux/mkl/lib/intel64 to let petsc pick the
> right libs for you.
>

 This used to work, but does not work any more.

Thanks,

Fande,


>
> Hong (Mr.)
>
>
> On May 3, 2018, at 11:32 AM, Fande Kong  wrote:
>
> --with-blaslapack-lib=-mkl -L' + os.environ['MKLROOT'] + '/lib/intel64
>
> works.
>
> Fande,
>
> On Thu, May 3, 2018 at 10:09 AM, Satish Balay  wrote:
>
>> Ok you are not 'building blaslapack' - but using mkl [as per
>> configure.log].
>>
>> I'll have to check the issue. It might be something to do with using
>> mkl as a static library..
>>
>> Hong might have some suggestions wrt theta builds.
>>
>> Satish
>>
>> On Thu, 3 May 2018, Satish Balay wrote:
>>
>> > Perhaps you should use MKL on theta? Again check
>> config/examples/arch-cray-xc40-knl-opt.py
>> >
>> > Satish
>> >
>> > On Thu, 3 May 2018, Kong, Fande wrote:
>> >
>> > > Thanks,
>> > >
>> > > I get the PETSc complied, but theta does not like the shared lib, I
>> think.
>> > >
>> > > I am switching back to a static lib.   I ever successfully built and
>> ran
>> > > the PETSc with the static compiling.
>> > >
>> > > But I encountered a problem this time on building blaslapack.
>> > >
>> > >
>> > > Thanks,
>> > >
>> > > Fande
>> > >
>> > > On Tue, May 1, 2018 at 2:22 PM, Satish Balay 
>> wrote:
>> > >
>> > > > This is theta..
>> > > >
>> > > > Try: using --LDFLAGS=-dynamic option
>> > > >
>> > > > [as listed in config/examples/arch-cray-xc40-knl-opt.py]
>> > > >
>> > > > Satish
>> > > >
>> > > > On Tue, 1 May 2018, Kong, Fande wrote:
>> > > >
>> > > > > Hi All,
>> > > > >
>> > > > > I can build a static petsc library on a supercomputer, but could
>> not do
>> > > > the
>> > > > > same thing with " --with-shared-libraries=1".
>> > > > >
>> > > > > The log file is attached.
>> > > > >
>> > > > >
>> > > > > Fande,
>> > > > >
>> > > >
>> > > >
>> > >
>> >
>> >
>>
>>
>
>

Re: [petsc-users] Could not determine how to create a shared library!

[Zhang, Hong]

Alternatively you can use 
--with-blaslapack-dir=/opt/intel/compilers_and_libraries/linux/mkl/lib/intel64 
to let petsc pick the right libs for you.

Hong (Mr.)

On May 3, 2018, at 11:32 AM, Fande Kong 
> wrote:

--with-blaslapack-lib=-mkl -L' + os.environ['MKLROOT'] + '/lib/intel64

works.

Fande,

On Thu, May 3, 2018 at 10:09 AM, Satish Balay 
> wrote:
Ok you are not 'building blaslapack' - but using mkl [as per configure.log].

I'll have to check the issue. It might be something to do with using
mkl as a static library..

Hong might have some suggestions wrt theta builds.

Satish

On Thu, 3 May 2018, Satish Balay wrote:

> Perhaps you should use MKL on theta? Again check 
> config/examples/arch-cray-xc40-knl-opt.py
>
> Satish
>
> On Thu, 3 May 2018, Kong, Fande wrote:
>
> > Thanks,
> >
> > I get the PETSc complied, but theta does not like the shared lib, I think.
> >
> > I am switching back to a static lib.   I ever successfully built and ran
> > the PETSc with the static compiling.
> >
> > But I encountered a problem this time on building blaslapack.
> >
> >
> > Thanks,
> >
> > Fande
> >
> > On Tue, May 1, 2018 at 2:22 PM, Satish Balay 
> > > wrote:
> >
> > > This is theta..
> > >
> > > Try: using --LDFLAGS=-dynamic option
> > >
> > > [as listed in config/examples/arch-cray-xc40-knl-opt.py]
> > >
> > > Satish
> > >
> > > On Tue, 1 May 2018, Kong, Fande wrote:
> > >
> > > > Hi All,
> > > >
> > > > I can build a static petsc library on a supercomputer, but could not do
> > > the
> > > > same thing with " --with-shared-libraries=1".
> > > >
> > > > The log file is attached.
> > > >
> > > >
> > > > Fande,
> > > >
> > >
> > >
> >
>
>

Re: [petsc-users] Could not determine how to create a shared library!

[Fande Kong]

--with-blaslapack-lib=-mkl -L' + os.environ['MKLROOT'] + '/lib/intel64

works.

Fande,

On Thu, May 3, 2018 at 10:09 AM, Satish Balay  wrote:

> Ok you are not 'building blaslapack' - but using mkl [as per
> configure.log].
>
> I'll have to check the issue. It might be something to do with using
> mkl as a static library..
>
> Hong might have some suggestions wrt theta builds.
>
> Satish
>
> On Thu, 3 May 2018, Satish Balay wrote:
>
> > Perhaps you should use MKL on theta? Again check
> config/examples/arch-cray-xc40-knl-opt.py
> >
> > Satish
> >
> > On Thu, 3 May 2018, Kong, Fande wrote:
> >
> > > Thanks,
> > >
> > > I get the PETSc complied, but theta does not like the shared lib, I
> think.
> > >
> > > I am switching back to a static lib.   I ever successfully built and
> ran
> > > the PETSc with the static compiling.
> > >
> > > But I encountered a problem this time on building blaslapack.
> > >
> > >
> > > Thanks,
> > >
> > > Fande
> > >
> > > On Tue, May 1, 2018 at 2:22 PM, Satish Balay 
> wrote:
> > >
> > > > This is theta..
> > > >
> > > > Try: using --LDFLAGS=-dynamic option
> > > >
> > > > [as listed in config/examples/arch-cray-xc40-knl-opt.py]
> > > >
> > > > Satish
> > > >
> > > > On Tue, 1 May 2018, Kong, Fande wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > I can build a static petsc library on a supercomputer, but could
> not do
> > > > the
> > > > > same thing with " --with-shared-libraries=1".
> > > > >
> > > > > The log file is attached.
> > > > >
> > > > >
> > > > > Fande,
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>

Re: [petsc-users] Could not determine how to create a shared library!

[Satish Balay]

Ok you are not 'building blaslapack' - but using mkl [as per configure.log].

I'll have to check the issue. It might be something to do with using
mkl as a static library..

Hong might have some suggestions wrt theta builds.

Satish

On Thu, 3 May 2018, Satish Balay wrote:

> Perhaps you should use MKL on theta? Again check 
> config/examples/arch-cray-xc40-knl-opt.py
> 
> Satish
> 
> On Thu, 3 May 2018, Kong, Fande wrote:
> 
> > Thanks,
> > 
> > I get the PETSc complied, but theta does not like the shared lib, I think.
> > 
> > I am switching back to a static lib.   I ever successfully built and ran
> > the PETSc with the static compiling.
> > 
> > But I encountered a problem this time on building blaslapack.
> > 
> > 
> > Thanks,
> > 
> > Fande
> > 
> > On Tue, May 1, 2018 at 2:22 PM, Satish Balay  wrote:
> > 
> > > This is theta..
> > >
> > > Try: using --LDFLAGS=-dynamic option
> > >
> > > [as listed in config/examples/arch-cray-xc40-knl-opt.py]
> > >
> > > Satish
> > >
> > > On Tue, 1 May 2018, Kong, Fande wrote:
> > >
> > > > Hi All,
> > > >
> > > > I can build a static petsc library on a supercomputer, but could not do
> > > the
> > > > same thing with " --with-shared-libraries=1".
> > > >
> > > > The log file is attached.
> > > >
> > > >
> > > > Fande,
> > > >
> > >
> > >
> > 
> 
> 

Re: [petsc-users] Could not determine how to create a shared library!

[Satish Balay]

Perhaps you should use MKL on theta? Again check 
config/examples/arch-cray-xc40-knl-opt.py

Satish

On Thu, 3 May 2018, Kong, Fande wrote:

> Thanks,
> 
> I get the PETSc complied, but theta does not like the shared lib, I think.
> 
> I am switching back to a static lib.   I ever successfully built and ran
> the PETSc with the static compiling.
> 
> But I encountered a problem this time on building blaslapack.
> 
> 
> Thanks,
> 
> Fande
> 
> On Tue, May 1, 2018 at 2:22 PM, Satish Balay  wrote:
> 
> > This is theta..
> >
> > Try: using --LDFLAGS=-dynamic option
> >
> > [as listed in config/examples/arch-cray-xc40-knl-opt.py]
> >
> > Satish
> >
> > On Tue, 1 May 2018, Kong, Fande wrote:
> >
> > > Hi All,
> > >
> > > I can build a static petsc library on a supercomputer, but could not do
> > the
> > > same thing with " --with-shared-libraries=1".
> > >
> > > The log file is attached.
> > >
> > >
> > > Fande,
> > >
> >
> >
> 

Re: [petsc-users] Could not determine how to create a shared library!

[Satish Balay]

This is theta..

Try: using --LDFLAGS=-dynamic option

[as listed in config/examples/arch-cray-xc40-knl-opt.py]

Satish

On Tue, 1 May 2018, Kong, Fande wrote:

> Hi All,
> 
> I can build a static petsc library on a supercomputer, but could not do the
> same thing with " --with-shared-libraries=1".
> 
> The log file is attached.
> 
> 
> Fande,
>