On Wed, Aug 2, 2023 at 9:32 AM maitri ksh <maitri....@gmail.com> wrote:
> I could compile petsc using the newer version of gnu compiler. > However, there is some unusual error when I tried to test petsc using a > print 'hello' file. I could not interpret what the error ('*error.txt*') > is, but it says something related to MATLAB (which is not used in the ' > *hello.c*' script). Any comments/suggestions? > 1) Did you link PETSc against MATLAB? If not, did you link your test against MATLAB? 2) If you linked PETSc against it, likely you were in a shell with LD_LIBRARY_PATH defined so that MATLAB would run. Without that, it cannot find the dynamic libraries it needs. Thanks, Matt > On Wed, Aug 2, 2023 at 11:07 AM maitri ksh <maitri....@gmail.com> wrote: > >> Okay, thank you. >> >> On Tue, Aug 1, 2023 at 9:43 PM Satish Balay <ba...@mcs.anl.gov> wrote: >> >>> > gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44) >>> >>> Is it possible for you to use a newer version GNU compilers? >>> >>> If not - your alternative is to build PETSc with --with-cxx=0 option >>> >>> But then - you can't use --download-superlu_dist or any pkgs that need >>> c++ [you could try building them separately though] >>> >>> Satish >>> >>> >>> On Tue, 1 Aug 2023, maitri ksh wrote: >>> >>> > I am trying to compile petsc on a cluster ( x86_64-redhat-linux, ' >>> > *configure.log'* is attached herewith) . Initially I got an error >>> related >>> > to 'C++11' flag, to troubleshoot this issue, I used 'CPPFLAGS' and >>> > 'CXXFLAGS' and could surpass the non-compliant error related to c++ >>> compiler >>> > but now it gives me another error 'cannot find a C preprocessor'. How >>> to >>> > fix this? >>> > >>> >>> -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>