[petsc-dev] problem with hypre with '--with-openmp=1'

Kong, Fande fande.kong at inl.gov
Wed Jun 27 12:10:53 CDT 2018


I was able to build hypre on theta (KNL) by adding the following two lines
of code to hypre.py

args.append('--host')
args.append('--host-alias')

It might help.


Fande Kong,

On Wed, Jun 27, 2018 at 10:39 AM, Satish Balay <balay at mcs.anl.gov> wrote:

> >>>>>>>>>
> Configure Options: --configModules=PETSc.Configure --optionsModule=config.compilerOptions
> --with-cc=cc --with-cxx=CC --with-fc=ftn COPTFLAGS="  -g -fp-model fast
> -xMIC-AVX512 -qopt-report=5  -hcpu=mic-knl -qopenmp-simd" CXXOPTFLAGS="-g
> -fp-model fast -xMIC-AVX512 -qopt-report=5  -hcpu=mic-knl -qopenmp-simd"
> FOPTFLAGS="  -g -fp-model fast -xMIC-AVX512 -qopt-report=5  -hcpu=mic-knl
> -qopenmp-simd" --download-metis=1 --with-hypre-dir=/global/homes/m/madams/tmp/hypre
> --download-parmetis=1 --download-fblaslapack --with-debugging=0
> --with-mpiexec=srun --with-batch=0 --known-mpi-shared-libraries=1
> --known-64-bit-blas-indices=0 --with-64-bit-indices=0
> PETSC_ARCH=arch-cori-knl-opt-intel-omp --with-openmp=1 --download-p4est=0
> --prefix=/global/homes/m/madams/petsc_install/petsc-cori-knl-opt-intel-omp
> --download-hdf5
> Wo
>
>               HYPRE: UserSpecified DirPath not found.. skipping:
> /global/homes/m/madams/tmp/hypre/lib
>               HYPRE: UserSpecified DirPath not found.. skipping:
> /global/homes/m/madams/tmp/hypre/lib64
>
> <<<<<<<<
>
> What do you have for:
>
> ls /global/homes/m/madams/tmp/hypre
> ls /global/homes/m/madams/tmp/hypre/lib
>
> Satish
>
>
> On Wed, 27 Jun 2018, Mark Adams wrote:
>
> > >
> > >
> > > In this case you can try:
> > >
> > > ./configure --download-hypre=1 --prefix=$HOME/soft/hypre
> --with-openmp=1
> > > PETSC_ARCH=arch-hypreinstall
> > > ./configure --with-hypre-dir=$HOME/soft/hypre
> > > PETSC_ARCH=my-regular-build-arch [and no openmp option]
> > > make PETSC_ARCH=my-regular-build-arch
> > >
> > >
> > This syntax for the hypre dir does not seem to work ...
> >
> >
> > > One caveat: sometimes - mixing openmp compiled code with non-openmp
> > > build of PETSc can give link errors [as compilers/linkers do different
> > > stuff internally during linktime] - so this might not always work.
> > >
> > > Satish
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20180627/de92c960/attachment.html>


More information about the petsc-dev mailing list