Brilliant! Thanks Terje and Johannes, this has led me on the right track. Terje: yes, the "module load" was done in the same shell. It did indeed adjust the PATH but did not set the CC/CXX variables. I tried setting them and got some strange errors which I couldn't intepret. So I tried the alternative approach of copying and adapting the profile which Johannes sent me. Initially, I got similarly strange tracebacks as before, but it turned out this was due to me having a comment line inside the PROLOGUE definition (I hadn't realised that the YAML syntax disallows this). After fixing this, the compilation ran through without problems.
Many thanks for your help! Best wishes, Max 2015-01-20 11:06 GMT+00:00 Johannes Ring <[email protected]>: > On Tue, Jan 20, 2015 at 11:56 AM, Maximilian Albert > <[email protected]> wrote: > > Hi, > > > > Just for background: I'm having another attempt to compile FEniCS on our > > local cluster using hashdist. Previously I had tried to do this by > manually > > cloning hashdist/hashstack and using a custom adaptation of the profile > > "hashstack/examples/fenics-1.4.0.rhel6.yaml". But since I never got this > to > > work I decided to start from scratch with the new repository that Anders > > mentioned in a previous email. > > > > Here are the steps I did with my new attempt: > > > > git clone https://bitbucket.org/fenics-project/fenics-install.git > > cd fenics-developer-tools/install > > bash fenics-install.sh > > > > I know that this uses the profile "profiles/fenics.Debian.yaml" and that > > this is likely to fail on a Red Hat system (which is what our cluster > uses). > > But I though it would be a good start to see where it fails. > > > > Somewhat to my surprise, all packages compile without problems until it > > fails to build dolfin. Here is the relevant part of the error message: > > > > 2015/01/20 10:29:58 - INFO: [package:run_job] -- The C compiler > > identification is GNU 4.4.6 > > 2015/01/20 10:29:58 - INFO: [package:run_job] -- The CXX compiler > > identification is GNU 4.4.6 > > 2015/01/20 10:29:58 - INFO: [package:run_job] -- Check for working C > > compiler: /usr/bin/cc > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Check for working C > > compiler: /usr/bin/cc -- works > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Detecting C compiler ABI > > info > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Detecting C compiler ABI > > info - done > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Check for working CXX > > compiler: /usr/bin/c++ > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Check for working CXX > > compiler: /usr/bin/c++ -- works > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Detecting CXX compiler > ABI > > info > > 2015/01/20 10:29:59 - INFO: [package:run_job] -- Detecting CXX compiler > ABI > > info - done > > 2015/01/20 10:29:59 - INFO: [package:run_job] CMake Error at > > CMakeLists.txt:25 (message): > > 2015/01/20 10:29:59 - INFO: [package:run_job] GCC version must be at > least > > 4.6 (for sufficient C++11 support. You have > > 2015/01/20 10:29:59 - INFO: [package:run_job] version 4.4.6 > > > > Obviously the problem is an outdated compiler. Our cluster provides both > gcc > > 4.8.1 and 4.9.1 via the module system, and I did load version 4.8.1 > before > > starting the FEniCS installation: > > > > $ which gcc > > /local/software/gcc/4.8.1/bin/gcc > > > > But somehow hashdist doesn't seem to pick this up. How can I point > hashdist > > to the correct compiler, and why doesn't it pick it up automatically? > > See for instance this example profile in hashstack: > > > https://github.com/hashdist/hashstack/blob/master/examples/fenics.abel.gnu.yaml > > Here we use the module system to set the compiler in the PROLOGUE. > > Johannes >
_______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
