Lines Matching refs:compiler

34 - If you do not have a Fortran compiler or [MPICH](https://www.mpich.org/) installed
48   installed in default system/compiler locations and `mpicc`, `mpif90`, mpiexec are available
82 - Build Complex version of PETSc (using c++ compiler):
120 It's best to use MPI compiler wrappers [^id9]. This can be done by either specifying
133 See {any}`doc_config_mpi` for details on how to select specific MPI compiler wrappers or the
134 specific compiler used by the MPI compiler wrapper.
137 - If a Fortran compiler is not available or not needed - disable using:
143 - If a c++ compiler is not available or not needed - disable using:
165 `configure` cannot detect compiler libraries for certain set of compilers. In this
166 case one can specify additional system/compiler libraries using the `LIBS` option:
188 - The packages are installed with the same compilers and compiler options as PETSc
294 - When fortran compiler is present:
300 - Or when configuring without a Fortran compiler - i.e `--with-fc=0`:
368 - The Intel MPI library provides MPI compiler wrappers with compiler specific names.
403   automatically become MPI compiler wrappers.
409 - Instead of providing the MPI compiler wrappers, one can provide the MPI installation directory, w…
438   behavior of the compiler-specific MPI compiler wrappers `mpigcc`, `mpigxx`, `mpif90`, `mpiicx`,
446 by MPI compiler wrappers `mpicc`/`mpif90` etc. require `$LD_LIBRARY_PATH` to be set to the
475 …ovides `/usr/bin/gcc`, which is, confusingly, a link to the `clang` compiler, not the GNU compiler.
486 This installs gfortran, gcc, and g++ with the compiler names
635 …eed to be installed separately (perhaps with MPI). Now use tau_cc.sh as compiler to PETSc configur…
744 …rs, they are commonly named `mpicc`, `mpicxx`, and `mpif90`. We call these "MPI compiler wrappers".