#782 external modules, e.g. dune-pdelab, do not build on top of the 2.0 release
Metadata
Property | Value |
---|---|
Reported by | Bernd Flemisch (bernd@iws.uni-stuttgart.de) |
Reported at | Apr 26, 2010 08:30 |
Type | Bug Report |
Version | 2.0beta |
Operating System | Unspecified / All |
Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Last edited at | Apr 26, 2010 09:26 |
Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Closed at | Apr 26, 2010 09:26 |
Closed in version | Unknown |
Resolution | Fixed |
Comment |
Description
I guess that that is a continuation of #769 (closed).
I cannot build any external modules on top of the 2.0 release. E.g., trying to build the current (r466) svn dune-pdelab by running dunecontrol --opts=optim.opts --module=dune-pdelab all gives
--- calling all for dune-pdelab --- --- calling autogen for dune-pdelab --- Found am directory /temp/bernd/DUMUX/dune-common-2.0/am --> dunedoxynize... Error: dunedoxynize global style not found --- Failed to build dune-pdelab --- Execution of dunecontrol terminated due to errors!
I attach my .opts file. Changing from enable-documentation to disable-documentation does not help.