Open cjlegg opened 1 year ago
Updated title to add additional requester, IN06035337.
The Python-based installer is quite awkward, but at least means it compartmentalises its own PETSc installation.
The first requester linked to some information from Delft about how they do the installation that might be useful: https://doc.dhpc.tudelft.nl/delftblue/howtos/firedrake/
I'm also trying a container-based installation in case that becomes necessary.
It seems like part of the MPICH configure step tests for a feature too new for GCC 4.9.2, and errors out. Trying with GCC 10.2.0.
Stated dependencies it needs externally:
- A C and C++ compiler (for example gcc/g++ or clang), GNU make
- A Fortran compiler (for PETSc)
- Blas and Lapack
- Boost
- Git
- Python version >=3.6
- The Python headers
- autoconf, automake, libtool
- CMake
- zlib, bison, flex
But then it creates a virtualenv and installs a lot of stuff into it, straight out of git repositories. Including MPICH. It seems possible to make it use an external MPI installation if preferred.
python3 firedrake-install --disable-ssh --no-package-manager
--disable-ssh
makes it not try to use SSH to access git repositories. (Why is that even the default???)--no-package-manager
makes it not try to use sudo apt-get
to install its external dependencies.
Package: Firedrake Detail: Ticket includes link to install instructions - problem is use of apt-get therein Ticket/requester: IN05869711 Cluster: Myriad