0

Error compiling TOUGH3

petsc-configure-err.log petsc-configure-out.log

Hello, 

 

I am trying to compile TOUGH3 in Ubuntu (Windows subsystem for Linux 2),

./complie_T3_Linux.sh 1

I get an error message "Script ERROR: Failed to build TOUGH TPLS" at "Performing configure step for 'petsc'".

 

I changed "PETSC_VERSION_PATCH 6" to "4", deleted 'build' and 'tough3-install' folders and reconfigured, but the error message is the same. 

 

I guess I need to check "petsc-configure-err.log" at /esd-tough3/build/tpl-build/tpls/petsc/petsc-timestamps.

However, I cannot figure out what this error is. 

I attach the log file. 

 

Would you please help me fix this problem ?

Thank you very much for your help. 

 

Hwajung

10 replies

null
    • Temitope
    • 2 yrs ago
    • Reported - view

    I am having the same issue. Did you fix it? 

    Thank you

    • Barbara_Carrera
    • 1 yr ago
    • Reported - view

    I am having the same issue. I also downloaded and compiled the BLAS and LAPACK packages separately to fix some other errors. Is it not possible to compile TOUGH without compiling PETSC again if you already have it compiled?
    The package python-is-python2 is replaced with  python-is-python3 and python3 is not accepted. I created a symbolic link in /usr/bin/env/ptyhon to /usr/bin/python2, but still python is not found.

    petsc-configure-err.log petsc-configure-out.log
      • Keurfon_Luu
      • 1 yr ago
      • Reported - view

      Barbara Carrera Can you try the following commands? 

      sudo apt update
sudo apt upgrade
sudo apt install gcc gfortran mpich cmake libblas-dev liblapack-dev python2 python

      Then, run Python: 

      python

      And make sure that it's Python 2.7 that is called.

      • Barbara_Carrera
      • 1 yr ago
      • Reported - view

      Keurfon Luu , that did not work, but I used this command instead: 

      sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 10

      Now Python 2.7 is called with the command python. However, now there is an issue with AZTEC. I will search the forum for it next.

      • kenny
      • 1 yr ago
      • Reported - view

      Barbara Carrera 

      Yes, you can compile TOUGH without repeat compiling PETSC again. Please have a look a look of following post for a solution:

      https://tough.forumbee.com/t/g9h57pf/tough3-installation-issue

      • Hwajung_Yoo
      • 1 yr ago
      • Reported - view

      Barbara Carrera 

      Hi,

      After solving the Python issue, I also faced several issues with AZTEC. 

       

      In my case, I made a few modifications related to AZTEC. 

      First, I commented out Line 16 (endif ()) of esd-toughlib/tpls/templates/aztec-configure-step.cmake.in to solve the first error. 

      Then, another error appeared in compiling, so I commented out line 16 (-D CMAKE_Fortran_FLAGS=@CMAKE_Fortran_FLAGS@) of esd-toughlib/tpls/templates/aztec-configure-step.sh.in.

       

      For the use of PETSc, I followed the post by Kenny, and it worked.

      error2 in aztec error1 in aztec
      • Barbara_Carrera
      • 1 yr ago
      • Reported - view

      Kenny Did you run into any problems with AZTEC? I used your modified installation package and now have trouble building this library. I solved the PETSC issue by downloading and installing it separately and pointing to it as you describe in your documentation. I can't find a similar solution for AZTEC, though.

      AZTEC-configure-out.log AZTEC-configure-err.log
      • kenny
      • 1 yr ago
      • Reported - view

      Barbara Carrera 

      I can not duplicate the problem on my computer. AZTEC requires less effort for compilation. I did not separate it from the TOUGH3. We are preparing a minor updated version of  TOUGH3 which  is expected to solve most TOUGH3 compilation problems.

      • Barbara_Carrera
      • 1 yr ago
      • Reported - view

      Kenny Thank you. The strange part is that I can change into the aztec directory and run the make command and everything works fine. It is just when I run the configure.sh for TOUGH when the problem arises. When do you expect the release of the updated version?

Login to reply

Content aside

  • 1 yr agoLast active
  • 10Replies
  • 265Views
  • 5 Following