Hi, It may look like it starts from the beginning, because the fenics-install.sh script will download hashdist, hashstack and fenics-developer-tools every time you run it. However, the other packages will be stored in ~/.hashdist (unless you modify ~/.hashdist/config.yaml) and it will not build them again unless you change the hashdist profile. I see from your terminal output that there is a problem downloading openssl. This problem can be fixed by adding a source cache mirror to fenicsproject.org. To do this, add the following line under source_caches in ~/.hashdist/config.yaml:
- url: http://fenicsproject.org/pub/hashdist/src Note that on a cluster it might be better to download hashdist and hashstack manually instead of using the fenics-install.sh script. This gives you better control and you can setup a hashdist profile to use modules from the cluster, like compiler and MPI modules. See for instance the fenics.abel.gnu.yaml example in hashstack. Johannes On Tue, Sep 22, 2015 at 8:00 AM Sladkova < [email protected]> wrote: > Hi, > > I am an PhD student using Fenics for my thesis and we are trying to > installing FEnics also on our cluster (LPGN, University of Nantes). I > would like to ask you a question regarding this installation. > > Exist there a way how to tell Fenics that he doesn't have to start the > installation from beginning? And that he can start the installation from > the point where he stopped the last time by for example giving him > what's still missing? > > For example: fenics-install.sh downloads lot of thing, most of them > already exists on the cluster. But he doesn't look for them, he just > starts from the beginning. However sometimes the distant server doesn't > respond quickly enough and everything stops. At this point we would like > to start from the point where we stopped before. > > I am also attaching a text file with an example of this problem. > > Thank you very much for your time, > Katerina Sladkova > _______________________________________________ > fenics-support mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics-support >
_______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
