Can we document this somewhere so that we can point to it? Perhaps on the web page?
Note that the above steps listed by Johannes is exactly what the fenics-install.sh script does: it clones HashDist + HashStack, calls the hit command with the right profile and then sets those environment variables. Maybe there's a way to make fenics-install.sh less of a blackbox, or make it print or explain the manual steps along the way so those who need it can customize the process. -- Anders Wed Feb 04 2015 at 8:50:02 AM skrev Johannes Ring <[email protected]>: > On Tue, Feb 3, 2015 at 8:53 PM, Laboure, Vincent M > <[email protected]> wrote: > > Thank you for the answer! > > > > Being unfamiliar with HashDist though, I want to make sure I understood > > correctly. > > > > I see that a .hashdist has been created in my home directory. Is that in > > that directory that I need to find a hashstack folder where I can paste > > examples/fenics.abel.gnu.yaml ? > > (I also tried: git clone http://hashdist.github.io but this returned an > > error) > > > > And to edit default.yaml, what I need to do is to add: > > > > packages: > > ... > > dolfin: > > toolset: /path/to/where/the/correct/gcc/version/is > > build_with: | > > openblas, suitesparse, scotch, parmetis, petsc, slepc, zlib, hdf5, > > vtk, cgal, bzip2 > > > > > > Is that correct? > > No. First get HashDist and HashStack from github: > > git clone https://github.com/hashdist/hashdist.git > git clone https://github.com/hashdist/hashstack.git > > Then enter the hashstack folder and setup your profile, for instance: > > cd hashstack > cp examples/fenics.abel.gnu.yaml default.yaml > > Modify default.yaml for your needs. See the PROLOGUE parameter for how > to use the module command if your system uses Environment Modules. > When you are satisfied with your profile, run > > ../hashdist/bin/hit build > > When the build is finished, you will have a new folder 'default' in > the hashstack folder with the new FEniCS installation. To use this > installation, setup your environment variables with something like > this: > > PREFIX=/path/to/hashstack/default > export PATH=$PREFIX/bin:$PATH > export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH > export MANPATH=$PREFIX/share/man:$MANPATH > export CMAKE_PREFIX_PATH=$PREFIX:$CMAKE_PREFIX_PATH > > You might also need to set LD_LIBRARY_PATH and PYTHONPATH, but that is > usually not needed: > > export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH > export PYTHONPATH=$PREFIX/lib/python2.7/site-packages:$PYTHONPATH > > Johannes > > > Thanks! > > > > On Mon, Feb 2, 2015 at 3:22 PM, Jan Blechta <[email protected]> > > wrote: > >> > >> On Mon, 2 Feb 2015 15:09:30 -0600 > >> "Laboure, Vincent M" <[email protected]> wrote: > > > > > >> > >> > [package:run_job] CMake Error at CMakeLists.txt:25 (message): > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] GCC version must be at > >> > least 4.6 (for sufficient C++11 support. You have > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] version 4.4.6 > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] -- Configuring > >> > incomplete, errors occurred! > >> > 2015/02/02 12:05:50 - INFO: [package:run_job] See also > >> > > >> > "/home/user1/.hashdist/tmp/dolfin-sd2jntuwgyab/_build/ > CMakeFiles/CMakeOutput.log". > >> > 2015/02/02 12:05:50 - ERROR: [package:run_job] Command '[u'/bin/bash', > >> > '_hashdist/build.sh']' returned non-zero exit status 1 > >> > 2015/02/02 12:05:50 - ERROR: [package:run_job] command failed > >> > (code=1); raising > >> > > >> > It seems that the problem comes from the GCC version. On this cluster, > >> > several versions of gcc are available (gcc-4.7.2, gcc-4.8.2 and > >> > gcc-4.9.1) but when I try to load them and rerun the fenics > >> > installation, I still get the same error... > >> > > >> > What would be the way to specify which GCC version to use? > >> > >> You have to customize the receipt. See for instance > >> > >> https://github.com/hashdist/hashstack/blob/master/ > examples/fenics.abel.gnu.yaml > >> > >> I think you can do something like > >> > >> #clone hashdist, hashstack > >> cd hashstack > >> cp examples/fenics.abel.gnu.yaml default.yaml > >> edit default.yaml > >> hit build > >> > >> Jan > >> > >> > >> > > > _______________________________________________ > 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
