PETSc supports both --prefix and inplace install.
Suggest using inplace install - in your $HOME:
For ex:
>>>
balay@p1 /home/balay
$ tar -xzf petsc-3.19.
petsc-3.19.2.tar.gz petsc-3.19.3.tar.gz
balay@p1 /home/balay
$ tar -xzf petsc-3.19.3.tar.gz
balay@p1 /home/balay
$ cd petsc-3.19.3
balay@p1
When configuring and making PETSc, PETSC_DIR can be empty or point to the
directory with the PETSc source
If you used --prefix to configure and install PETSc then
When using PETSc to compile other source code and using a makefile that
utilizes PETSC_DIR, then PETSC_DIR needs to poi
So I have this to go by:
export PETSC_DIR=/absolute/path/to/petsc
export PETSC_ARCH=linux-gnu-c-debug
PETSC_DIR Is that the installation/destination path or the path where the
source code is? I feel confused
So there is a destination folder that dolfinx project wnats for petsc. I have
an i
We do not recommend installing PETSc in /usr/include [aka --prefix=/usr]. Now
you have some petsc includes here that will potentially conflict with any other
install of PETSc you might attempt.
You might have to manually check - and delete PETSc installed files from here.
For most uses - one c
On Mon, Jul 17, 2023 at 10:55 AM philliprusso via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> I cloned petsc source for use with dolfinx project. So after .configure
> mak sudo make install I found there was some type of difficulty with the
> destination directory so I copied the files manuall
I cloned petsc source for use with dolfinx project. So after .configure mak
sudo make install I found there was some type of difficulty with the
destination directory so I copied the files manually into usr/includes of
Ubuntu 22.04 jammy. So some petsc header files are now found for compiling cp
