@prj
Dear Pierre,
When installing FreeFem++ from sources (develop branch) to a new computer with Ubuntu 24, I get an error when running make petsc-slepc.
It gives
=============================================================================================
Compiling OpenBLAS; this may take several minutes
=============================================================================================
*********************************************************************************************
UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):
---------------------------------------------------------------------------------------------
Error running make on
/home/fbouchut/FreeFem/FreeFem-sources/3rdparty/ff-petsc/petsc-3.24.4/fr/externalpackages/git.openblas
*********************************************************************************************
make: *** [Makefile:222 : petsc-3.24.4/tag-conf-real] Erreur 1
The configure.log (in 3rdparty/ff-petsc/petsc-3.24.4) is configure.log (1.9 MB)
Do you have a way to solve the issue?
Thank you for your reply
my gcc version is 13.3.0
I am a bit scared to update gcc, since it is the one that has been installed with the installation of ubuntu.
Indeed I have an “old” computer that I upgraded from ubuntu 22 to ubuntu 24 in january. It compiled the FreeFem develop banch successfully after this upgrade. It has also the gcc version 13.3.0
Then now I have a new computer, freshly installed with ubuntu 24, but it fails to compile FreeFem (it stops at OpenBLAS).
It is a bit mysterious. The old one is a HP EliteBook, the new one is a Lenovo Think Pad P14s.
Thus now instead of installing from source I have installed the FF 4.15 master branch from the .deb.
It works, but later it could be a problem if I am not able to install from source…
The issue comes from the compiler flags being passed to OpenBLAS. You could simply install OpenBLAS via aptitude and let PETSc compile the rest if you don’t feel like updating your compiler. I don’t know whether this particular issue has been reported to the OpenBLAS developers and if there is a fix coming in a newer release.