[petsc-users] petsc-users Digest, Vol 33, Issue 13

[Satish Balay]

Yes- moving binaries [between machines of the same OS] can work. But
practically other issues mentioned dominate [like mpi] that can cause
it not to work - hence its best to work at source level of
portability.

The Primary folks that have interest in this mode are comercial
software developers - who can put sufficient effort to address its
shortcommings.

We don't support such usage with PETSc. you are on your own with it.

Satish


On Wed, 7 Sep 2011, amrit poudel wrote:

> 
> HI Sean,It is really not the question of "not believing you", it is just that I do not have any formal training in programming/parallel programming and hence my misconceptions. I am simply trying to clear up my doubts by asking questions to experts. Please bear with me and accept my apology if you find any of my questions ridiculously incorrect. 
> 
> I found the following question in FAQ section of http://www.mcs.anl.gov/petsc/petsc-2/documentation/faq.html#already-installed . I know that this is related to shared libraries, but it sounds as if "moving libraries around" may be an option. Again, I assure you that I 100% believe you. I am simply trying to understand what this question is referring to.
> 
> 
> What
>                   do
>                   I
>                   do if I want to move
>                   my executable to a different machine?
>             You would also need to have access to the shared
>               libraries on this new machine. The other alternative is to
>               build the
>               exeutable without shared libraries by first deleting the
>               shared
>               libraries, and then creating the executable. 
> 
> 
> 
> Thanks for all your help !
> 
> 
> 
> 
> From: sean at mcs.anl.gov
> Date: Wed, 7 Sep 2011 19:31:29 +0000
> To: petsc-users at mcs.anl.gov
> Subject: Re: [petsc-users] petsc-users Digest, Vol 33, Issue 13
> 
> Sean mentioned that I will need to install PETSc on the actual cluster that I want to run my program, which, as I understand, means that I need to do ./configure make make install on that actual cluster I plan on running my code. I was originally thinking that if I do ./configure make make install on some Scientific Linux computer(with appropriate MPI), then I will get all the libraries (.a files) that I need. Then, if I have to run my program, say program.c, that calls PETSc libraries on a Scientific Linux cluster, all I need to do is carry all the libraries (and anything that my program is linked with) together with my program to the cluster and run my program there. Is this really incorrect ?
> 
> 
> That is 100% incorrect. If you don't believe me, you are welcome to try it on your own. You really have to give up on this "carry all the libraries around" idea.
> 
> 
> Sean