[petsc-users] error with xlib

[Satish Balay]

You can do with either of the following notation [from your shell]

./configure "CXXOPTFLAGS=-O2 -g -Xpreprocessor -fopenmp -I$(brew --prefix libomp)/include -L$(brew --prefix libomp)/lib -lomp"
or
./configure CXXOPTFLAGS="-O2 -g -Xpreprocessor -fopenmp -I$(brew --prefix libomp)/include -L$(brew --prefix libomp)/lib -lomp"

Satish

On Mon, 13 Apr 2020, Satish Balay via petsc-users wrote:

> This is very funky
> 
> >>>
> Configure Options: --configModules=PETSc.Configure --optionsModule=config.compilerOptions --with-mpi-dir=/usr/local/Cellar/mpich/3.3.2 COPTFLAGS="-O2 -g  -Xpreprocessor -fopenmp -I"$(brew --prefix libomp)/include" -L"$(brew --prefix libomp)/lib -lomp"" CXXOPTFLAGS="-O2 -g -Xpreprocessor -fopenmp -I"$(brew --prefix libomp)/include" -L"$(brew --prefix libomp)/lib -lomp"" FOPTFLAGS="-O2 -g -Xpreprocessor -fopenmp -I"$(brew --prefix libomp)/include" -L"$(brew --prefix libomp)/lib -lomp"" --download-parmetis=1 --download-metis=1 --download-hypre=1 --download-triangle=1 --download-p4est=1 --download-zlib --with-x=0 --download-ctetgen --with-debugging=0 --download-hdf5=1 PETSC_ARCH=arch-macosx-gnu-O-omp --with-openmp=1 --with-log=0 --with-threadsafety --download-chaco
> <<<
> 
> -I"$(brew --prefix libomp)/include" type options to configure doesn't make sense. You are using bash syntax here - and expecting configure to resolve it. Its best for your bash shell to evaluate this before passing this info to configure
> 
> Also --download-zlib isn't needed on OSX
> 
> Satish
> 
> 
> On Mon, 13 Apr 2020, Mark Adams wrote:
> 
> > Now that I look at it, I see:
> > 
> > CFLAGS="-fstack-protector -fno-stack-check -Qunused-arguments -O2 -g
> > -Xpreprocessor -fopenmp -I"$(brew --prefix libomp)/include" -L"$(brew
> > --prefix libomp)/lib -lomp""
> > prefix="/Users/markadams/Codes/petsc/arch-macosx-gnu-O-omp"
> > 
> > Note the two ". That does not look right. I use
> > 
> > 'COPTFLAGS=-O2 -g  -Xpreprocessor -fopenmp -I"$(brew --prefix
> > libomp)/include" -L"$(brew --prefix libomp)/lib -lomp" ',
> > 
> > I know how to do stuff like:
> > 
> > '--with-blaslapack-lib=-L' + os.environ['OLCF_NETLIB_LAPACK_ROOT'] +
> > '/lib64 -lblas -llapack'
> > 
> > Is there like and os.exec that I could use like this for my FLAGS?
> > 
> > 
> > 
> > On Mon, Apr 13, 2020 at 11:46 AM Matthew Knepley <knepley at gmail.com> wrote:
> > 
> > > On Mon, Apr 13, 2020 at 11:34 AM Mark Adams <mfadams at lbl.gov> wrote:
> > >
> > >> I get this error configuring zlib, osx, with OpenMP.
> > >> Any ideas?
> > >>
> > >
> > > This failed without output
> > >
> > > Executing: cd
> > > /Users/markadams/Codes/petsc/arch-macosx-gnu-O-omp/externalpackages/zlib-1.2.11
> > > && CC="/usr/local/Cellar/mpich/3.3.2/bin/mpicc" CFLAGS="-fstack-protector
> > > -fno-stack-check -Qunused-arguments -O2 -g -Xpreprocessor -fopenmp
> > > -I"$(brew --prefix libomp)/include" -L"$(brew --prefix libomp)/lib -lomp""
> > > prefix="/Users/markadams/Codes/petsc/arch-macosx-gnu-O-omp" ./configure  &&
> > > /usr/bin/make -j7 -l12.0 &&  /usr/bin/make install
> > >
> > > So execute each step in turn and see what fails.
> > >
> > >   Thanks,
> > >
> > >      Matt
> > >
> > >
> > >> Thanks,
> > >> Mark
> > >>
> > >
> > >
> > > --
> > > 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
> > >
> > > https://www.cse.buffalo.edu/~knepley/
> > > <http://www.cse.buffalo.edu/~knepley/>
> > >
> > 
>