Yes, you can remove the entire 'download' section from petsc. Can you show me the exact error message (attach build.log and configure.log from the temporary hashdist directory). I tried this myself now and I didn't have any problems.
Johannes On Thu, Sep 24, 2015 at 4:35 PM Guy Moebs <[email protected]> wrote: > > > Le 24/09/2015 16:26, Johannes Ring a écrit : > > Did you build PETSc manually? > > yes, I find its temporary directory, ~/.hashdist/tmp/petsc-labtr2b5ktog, > and I launch the configure in it with options for finding MPI, BLAS and > LAPack already built by fenics. > > > It is easier if you let fenics-install.sh do it. If it fails to download > ml, then just remove it from the profile (local.yaml). We can try to add it > back later if you need PETSc with ml. > > > OK, I remove ml from the files list to be download. I relaunch > fenics-install.sh > Now, It fails for scalapack that it is unable to download. Should I remove > it too from the dependance list in the local.yaml file ? > > Regards > > Guy. > > > > Johannes > > On Thu, Sep 24, 2015 at 3:45 PM Guy Moebs <[email protected]> > wrote: > >> Hello Johannes, >> >> Thank you for your message. It greatly helps me to go further. Now I >> encounter a problem inside the installation of PETSc. >> >> At configure step, it can't download ML, ie. ml-6.2-p2.tar.gz and propose >> to download it manually in order to use the configure option : >> --download-ml=/yourselectedlocation/ml-6.2-p2.tar.gz >> as a workaround. >> I try this and it works. I have compiled PETSc. >> >> Now, if I come back to fenics, how can I tell it that there is a compiled >> PETSc next to it and to use it ? >> >> If I relaunch the installation script of fenics, that is, >> ./install/fenics-install.sh , it begins a new installation of PETSc, just >> next to the right one with the same error about downloading ML. >> >> Regards, >> Guy. >> >> >> Le 23/09/2015 09:25, Johannes Ring a écrit : >> >> On Tue, Sep 22, 2015 at 3:43 PM Guy Moebs <[email protected]> >> wrote: >> >>> Hi Johannes, >>> >>> I'd like our users to be able to run fenics on our cluster. So a runable >>> version first, and next a maybe more optimized one. >>> >>> "gcc", /usr/bin/gcc, is version 4.3 of the GNU compiler. >>> >>> We have version 4.7 as /usr/bin/gcc-4.7 >>> Where is the hashdist profile file in order to modify the gcc default >>> name ? >>> >> >> You will have to create the hashdist profile, either from scratch or by >> modifying an existing profile. There are profiles that you can use in >> hashstack and in fenics-developer-tools. You can for example do the >> following: >> >> git clone >> https://bitbucket.org/fenics-project/fenics-developer-tools.git >> cd fenics-developer-tools >> cp install/profiles/fenics.Linux.yaml local.yaml >> >> Now, open local.yaml and add something like the following: >> >> parameters: >> PROLOGUE: | >> export CC=/usr/bin/gcc-4.7; export CXX=/usr/bin/g++-4.7; export >> FC=/usr/bin/gfortran-4.7 >> >> To use OpenMPI instead of MPICH, replace >> >> mpi: >> use: mpich >> >> with this: >> >> mpi: >> use: openmpi >> >> When you are satisfied with your profile, run >> >> ./install/fenics-install.sh >> >> The fenics-install.sh script will detect and use your local.yaml profile. >> >> Note that you should set the same variables when compiling/running FEniCS >> programs as you do in the PROLOGUE. In the case above, this will be >> >> source fenics.custom >> export CC=/usr/bin/gcc-4.7 >> export CXX=/usr/bin/g++-4.7 >> export FC=/usr/bin/gfortran-4.7 >> >> Johannes >> >> >> _______________________________________________ > 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
