[Dune] Configure failure with Dune 1.2beta1
Markus Blatt
Markus.Blatt at iwr.uni-heidelberg.de
Fri Mar 20 14:03:25 CET 2009
On Fri, Mar 20, 2009 at 01:25:25PM +0100, Bård Skaflestad wrote:
> and I run the build from the top-level directory as
>
> CC=gcc43 CXX=g++43 F77=gfortran43 \
> ./dune-common/bin/dunecontrol all \
> --enable-expressiontemplates \
> --with-blas=/usr/lib64 \
> --with-lapack=/usr/lib64 \
> --with-metis=/home/bska/tmp/downloads/SuiteSparse/metis-4.0/
>
Wow I was not aware that passing flags like this works with dunecontrol.
Just a comment: I am not really sure what the status of the
expression templates is. But I fear that they are not well tested.
> I have attached a type script of the installation process to this email in
> case you wish to investigate the issue any further. I don't know if it makes
> any difference, but the Doxygen process reports that
>
> $ cat dune-common/doc/doxygen/doxygen.log
> Error: tag INPUT: input source `./mainpage' does not exist
>
THis sounds like a serious bug. Normally the documentation should be
shipped with the tarballs and nothing should be built here.
Anyway you can skip building the documentation by using the
--disable-documentation configure flag.
Did you run make clean previously or was this build on prestine
dune-common?
Cheers,
Markus
More information about the Dune
mailing list