[petsc-users] [EXTERNAL] Re: Issue when installing PETSc

[Nils Tilton]

Dear Barry,

Thanks so much for your help. I was eventually able to get my code to compile and run correctly with PETSc. The other strange issues I alluded to in my email turned out to be unrelated. Thanks again!

Best Wishes,
Nils

From: Barry Smith <bsmith at petsc.dev>
Date: Friday, January 24, 2025 at 10:14 AM
To: Nils Tilton <ntilton at mines.edu>
Cc: petsc-users at mcs.anl.gov <petsc-users at mcs.anl.gov>
Subject: [EXTERNAL] Re: [petsc-users] Issue when installing PETSc
CAUTION: This email originated from outside of the Colorado School of Mines organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.




On Jan 23, 2025, at 10:05 PM, Nils Tilton <ntilton at mines.edu> wrote:

Dear PETSc Team,

I hope this email finds you all well. I have a question regarding installation of PETSc. I recently installed PETSc on Ubuntu 20.04.2 LTS. I followed the online instructions, whereby I first downloaded the files using git, and then ran “./configure” and then “make all check.” However, I noted two issues during this process. First, after running ./configure, I got the following text:

“Language used to compile PETSc: C”

This gave me the impression PETSc was compiled with C, but my code is written in C++. Is the above going to be an issue? I am attaching my configure.log and make.log files if that helps.

   No issue. You can use it fully from C++


The second issue is that when I ran “make all check,” I did get some errors in the final checking stage. These don’t appear in the make.log file, so I am attaching a screenshot. I seem to recall that screenshots are frowned upon when asking questions to the PETSc team. I apologize in advance. I just couldn’t find any other way to save the text.

I will add that I was able to successfully compile my C++ code that uses PETSc, but I am getting some funny behavior that could be related to the issues above. I am holding off on including those issues here to avoid complicating my question too soon.

  The "protocal" error message is from the MPI and can be ignored. Sadly MPI implementers still do not prefix their warning/error messages to indicate the are coming from MPI.

  So you are set to go, good luck

  Barry


Thank you very much for all your help!
Best Wishes,
Nils

<configure.log><make.log><Screenshot 2025-01-23 at 5.57.48 PM.png>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20250124/ec730a1d/attachment-0001.html>