Glad it worked! Thanks for the update.
Satish
On Tue, 10 Mar 2020, Cameron Smith wrote:
> Thank you.
>
> Using the spack spec
>
> petsc@3.7.7 ~hdf5 ~hypre ~superlu-dist cflags=-qsmp=omp fflags=-qsmp=omp
> cxxflags=-qsmp=omp
>
> and passing the same flags to a manual (non-spack) petsc 3.7.7 bu
Thank you.
Using the spack spec
petsc@3.7.7 ~hdf5 ~hypre ~superlu-dist cflags=-qsmp=omp fflags=-qsmp=omp
cxxflags=-qsmp=omp
and passing the same flags to a manual (non-spack) petsc 3.7.7 build
produced installs that do not list xlomp_ser in the configure.log.
Thank-you,
Cameron
On 3/10/20
Created an MR for this change
https://gitlab.com/petsc/petsc/-/merge_requests/2593
Satish
On Tue, 10 Mar 2020, Satish Balay via petsc-users wrote:
> Another option is to strip out -lxlomp_ser when parsing 'xlc -V' [as its a
> common library for all 3 language compilers]. i.e the following chan
Another option is to strip out -lxlomp_ser when parsing 'xlc -V' [as its a
common library for all 3 language compilers]. i.e the following change [this
change is on current maint - but similar change can be done with petsc-3.7]..
[This is easier than changing the order in which --with-openmp opt
That makes sense. Thank you.
-Cameron
On 3/10/20 9:25 AM, Satish Balay wrote:
PETSc configure attempts to check for compiler libraries [so that one
can mix and use c,c++,fortran codes with a c linker] by running
compilers in verbose mode - and parsing the output. [i.e checkCLibraries(),
check
PETSc configure attempts to check for compiler libraries [so that one
can mix and use c,c++,fortran codes with a c linker] by running
compilers in verbose mode - and parsing the output. [i.e checkCLibraries(),
checkFortranLibraries() ..]
Here IBM compiler is using different library internally bas
Thank you. I'll give that a shot.
Out of curiosity, how does passing the openmp flags relate to the
'--with-openmp' option described here:
https://www.mcs.anl.gov/petsc/documentation/installation.html
under 'Installing packages that utilize OpenMP'? Is this just passing
the openmp flags in
BTW: You might be able to do the same via spack.
spack install petsc@3.7.7 ~hdf5 ~hypre ~superlu-dist cflags=-fopenmp
fflags=-fopenmp cxxflags=-fopenmp
Satish
On Tue, 10 Mar 2020, Satish Balay via petsc-users wrote:
> Cameron,
>
> You can try changing following petsc configure options and see
Cameron,
You can try changing following petsc configure options and see if that works..
[i.e build petsc manually]
CFLAGS=-fopenmp FFLAGS=-fopenmp CXXFLAGS=-fopenmp
Satish
On Tue, 10 Mar 2020, Cameron Smith wrote:
> Thank you Mark.
>
> The configure.log is attached.
>
> Please let me know i
Hi Cameron,
This can go on the list and we always want the configure.log file.
I build on Summit, but have not used the XL compilers. I've built 3.7.7
with GNU and PGI. (XGC usually wants PGI)
On Mon, Mar 9, 2020 at 11:27 PM Cameron Smith wrote:
> Hello,
>
> I'm installing petsc 3.7.7 on a s
10 matches
Mail list logo
