[petsc-users] deactivating x11 in PETSc 3.13.0 with pastix/hwloc

[Satish Balay]

Great!

Wrt pastix dependency on hwloc - config/BuildSystem/config/packages/PaStiX.py has the following comment:

    # PaStiX.py does not absolutely require hwloc, but it performs better with it and can fail (in ways not easily tested) without it
    # https://gforge.inria.fr/forum/forum.php?thread_id=32824&forum_id=599&group_id=186
    # https://solverstack.gitlabpages.inria.fr/pastix/Bindings.html

I have a fix in branch balay/fix-hwloc-x-dependency/maint [that does not need the extra --download-hwloc-configure-arguments=--without-x option]. Can you give this a try?

Satish

On Mon, 6 Apr 2020, Alfredo Jaramillo wrote:

> hello Satish,
> adding
> --download-hwloc-configure-arguments=--without-x
> worked perfectly
> 
> thank you!
> 
> On Mon, Apr 6, 2020 at 2:12 PM Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > you can try:
> >
> > --download-pastix --download-hwloc
> > --download-hwloc-configure-arguments=--without-x
> >
> > We should fix this to automatically use --with-x=0/1
> >
> > Satish
> >
> > On Mon, 6 Apr 2020, Alfredo Jaramillo wrote:
> >
> > > hello everyone,
> > >
> > > I have a fresh installation of the 3.13.0 version with pastix. Like with
> > > previous versions, I'm using the options
> > >
> > > --with-x11=0 --with-x=0 --with-windows-graphics=0
> > >
> > > to disable X11
> > >
> > > however, when compiling my program foo and doing
> > >
> > > $ ldd foo
> > >
> > > between the linked libraries there appear:
> > > libXNVCtrl.so.0 and libX11.so.6
> > >
> > > the first one related to NVIDIA. I observed that this does not happen
> > when
> > > installing PETSc without hwloc. In this new version, PETSc requires to
> > > install hwloc when trying to install pastix. In previous versions of
> > PETSc
> > > (eg 3.11.2) that wasn't necessary.
> > >
> > > I'm working in a cluster where I have no access to these X11-related
> > > libraries and that's why I need them not be linked. Is it there some way
> > to
> > > disable X11 when installing hwloc? maybe enforcing some configuration
> > > variables when installing it through petsc or installing it
> > independently?
> > >
> > > thanks a lot!
> > >
> > > Below the configuration command of the two installations I've tried with
> > > the 3.13.0 version.
> > >
> > > =================== WITH PASTIX ===================
> > >
> > > ./configure --with-make-np=20
> > > --with-petsc-arch=x64go-3.13-openmpi-4.0.1-pastix-64 --with-debugging=0
> > > --doCleanup=0 \
> > > --with-mpi=1 \
> > > --with-valgrind=1 --with-valgrind-dir=$PATH_TO_VALGRIND/valgrind-3.15.0 \
> > > --download-scalapack \
> > > --download-openblas \
> > > --download-mumps \
> > > --download-superlu_dist \
> > > --download-metis \
> > > --download-parmetis \
> > > --download-ptscotch \
> > > --download-hypre \
> > >
> > > *--download-pastix \--download-hwloc \*
> > > --with-64-bit-indices=1 \
> > > LDFLAGS=$LDFLAGS CPPFLAGS=$CPPFLAGS \
> > > --with-cxx-dialect=C++11 \
> > > --with-x11=0 --with-x=0 --with-windows-graphics=0 \
> > > COPTFLAGS="-O3 -march=native -mtune=native" \
> > > CXXOPTFLAGS="-O3 -march=native -mtune=native" \
> > > FOPTFLAGS="-O3 -march=native -mtune=native"
> > >
> > > =================== WITHOUT PASTIX ===================
> > >
> > > the same as above but the options "--download-pastix --download-hwloc"
> > >
> > > ======================================================
> > >
> >
> >
>