Good morning Satish, I tried this solution and I could effectively link the libraries to the executable in a new machine. Nonetheless, I am having now a new problem when I am trying to execute my program on the new machine. Since the new machine does not have petsc nor mpi installed, the program throws me this error message (see image attached), but I do not want the final users to install mpi their own. Is it any solution to this issue? Can you help me, please? I am looking forward to hearing from you.
Best regards, Sebastian [image: imagen.png] El jue, 21 jul 2022 a las 15:36, Satish Balay (<ba...@mcs.anl.gov>) escribió: > You can try: > > ldd your-executable > > And copy over all the .so files listed by it [ignoring the system > libraries - that might be present on the remote machine > > > Try setting LD_LIBRARY_PATH to this location [n the new machine] > > and retry 'ldd your-executable' on the new machine - and make sure there > are no 'not found' libraries in that list > > then your-executable is likely to work. > > Note: this might not work parallely - as you would need mpiexec for a > parallel run > > Satish > > On Thu, 21 Jul 2022, Sebastian Gutierrez wrote: > > > > > > > > > Good afternoon PETSc Development Team, > > > > > > > > I have been trying to distribute your program as third party library in > my CMake Project. Because I do not want to my Linux users to have to > install petsc by their own. I just want them to use my final > > product that uses petsc dependencies. When I execute make install of my > Project in my own machine, it works perfectly but the problem appears when > I move the executable to another machine that does not have > > installed petsc. > > > > > > > > I honestly have no idea to solve this. I wrote this email in hopes that > you kindly help me out with this. > > > > I am looking forward to your answer. > > > > > > > > Best regards, > > > > > > > > Sebastian Gutierrez > > > > > > >
