On Wed, 14 Jan 2015 11:00:36 +0100 Jan Blechta <[email protected]> wrote:
> Can you try > > $ export CMAKE_CXX_COMPILER="/path/to/gcc4.9.2/bin/g++" @Johannes, this could do the job as a workaround but is not necessarily proper solution as distutils based installers like in FFC (used at least for running has_cxx_flag() in <ffc>/setup.py) will not see this, right? Maybe also mpi4py, petsc4py, slepc4py. Jan > > prior to running build? > > Jan > > > On Tue, 13 Jan 2015 12:31:24 -0600 > Justin Chang <[email protected]> wrote: > > > Jan, > > > > I get a new error now. This one occurs while trying to install > > dolfin: > > > > 2015/01/13 08:04:48 - INFO: [package:run_job] -- Detecting CXX > > compiler ABI info - done > > 2015/01/13 08:04:48 - INFO: [package:run_job] CMake Error at > > CMakeLists.txt:25 (message): > > 2015/01/13 08:04:48 - INFO: [package:run_job] GCC version must be > > at least 4.6 (for sufficient C++11 support. You have > > 2015/01/13 08:04:48 - INFO: [package:run_job] version 4.4.7 > > 2015/01/13 08:04:48 - INFO: [package:run_job] > > 2015/01/13 08:04:48 - INFO: [package:run_job] > > 2015/01/13 08:04:48 - INFO: [package:run_job] -- Configuring > > incomplete, errors occurred! > > 2015/01/13 08:04:48 - INFO: [package:run_job] See also > > "/home/jchang23/.hashdist/tmp/dolfin-qj5f4n3jajec/_build/CMakeFiles/CMakeOutput.log". > > 2015/01/13 08:04:48 - ERROR: [package:run_job] Command > > '[u'/bin/bash', '_hashdist/build.sh']' returned non-zero exit > > status 1 2015/01/13 08:04:48 - ERROR: [package:run_job] command > > failed (code=1); raising > > > > The default gcc compiler on my system is 4.4.7 so I had installed > > everything with that version. We actually have gcc 4.9.2 so I ran > > the script again after loading this version, but it still gave the > > same error. Do you know what could be causing this problem? > > > > Thanks, > > Justin > > > > On Tue, Jan 13, 2015 at 7:50 AM, Johannes Ring <[email protected]> > > wrote: > > > > > On Tue, Jan 13, 2015 at 1:17 PM, Justin Chang > > > <[email protected]> wrote: > > > > Jan, > > > > > > > > I tried the new installation method and when it came to > > > > installing > > > PETSc, it > > > > gave me this error: > > > > > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] > > > > > > > ******************************************************************************* > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] UNABLE to > > > CONFIGURE > > > > with GIVEN OPTIONS (see configure.log for details): > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] > > > > > > > ------------------------------------------------------------------------------- > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] Could not find a > > > > functional LAPACK. Run with --with-lapack-lib=<lib> to indicate > > > > the library > > > containing > > > > LAPACK. > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] Or > > > --download-fblaslapack=1 > > > > to have one automatically downloaded and installed > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] > > > > > > > ******************************************************************************* > > > > 2015/01/13 06:03:35 - INFO: [package:run_job] > > > > 2015/01/13 06:03:35 - ERROR: [package:run_job] Command > > > > '[u'/bin/bash', '_hashdist/build.sh']' returned non-zero exit > > > > status 1 2015/01/13 06:03:35 - ERROR: [package:run_job] command > > > > failed (code=1); raising > > > > > > I think this is similar to this problem: > > > https://github.com/hashdist/hashstack/issues/594. I have made some > > > changes to fenics-install now. Can you try again and see if it > > > fixes the problem for you? > > > > > > 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
