ly need Hypre for now, but if you have any clue on where to
> look next, that would be helpful
>
>
>
> Thanks again
>
>
>
> Paolo
>
>
>
> *Da: *Mark Adams
> *Inviato: *lunedì 3 ottobre 2022 13:20
> *A: *Paolo Lampitella
> *Cc: *petsc-users@mcs.anl.g
ause it is not
> > seeing the LLVM based compilers, only the intel classical ones. Yet the
> > variables seem correctly exported.
> >
> > Paolo
> >
> >
> > Da: Barry Smith <mailto:bsm...@petsc.dev>
> > Inviato: lunedì 3 o
> Paolo
>
>
> Da: Barry Smith <mailto:bsm...@petsc.dev>
> Inviato: lunedì 3 ottobre 2022 15:19
> A: Paolo Lampitella <mailto:paololampite...@hotmail.com>
> Cc: petsc-users@mcs.anl.gov <mailto:petsc-users@mcs.anl.gov>
> Oggetto: Re: [petsc-users] How to u
bsmith@petsc-01:~$ mpicc
This script invokes an appropriate specialized C MPI compiler driver.
The following ways (priority order) can be used for changing default
compiler name (gcc):
1. Command line option: -cc=
2. Environment variable: I_MPI_CC (current value '')
3. Environment
Hi Paolo,
You can use things like this in your configure file to set compilers and
options.
And you want to send us your configure.log file if it fails.
Mark
'--with-cc=gcc-11',
'--with-cxx=g++-11',
'--with-fc=gfortran-11',
'CFLAGS=-g',
'CXXFLAGS=-g',
'COPTFLAGS=-O0',
Dear PETSc users and developers,
as per the title, I recently installed the base and HPC Intel OneApi toolkits
on a machine running Ubuntu 20.04.
As you probably know, OneApi comes with the classical compilers (icc, icpc,
ifort) and relative mpi wrappers (mpiicc, mpiicpc, mpiifort) as well as
