#893 Module suggestions are inherited as dependencies.
Metadata
| Property | Value |
|---|---|
| Reported by | Robert K (robertk@posteo.org) |
| Reported at | Mar 7, 2011 11:02 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Jun 10, 2011 10:50 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Jun 10, 2011 10:50 |
| Closed in version | 2.2 |
| Resolution | Fixed |
| Comment | in r6458 |
Description
When configuring a module (e.g. dune-bar) that depends on another module (e.g. dune-foo) that has a suggested dependency (dune-istl) this fails because the suggestion in dune-foo suprisingly turns into a hard dependency in dune-bar.
The tar balls have to be build with dune-istl present. When using the tars to compile dune-common, dune-foo, and dune-bar the configuration fails in dune-bar with the following comment:
command: ./dune-common-2.2-svn/bin/dunecontrol all
.....
checking for dune-istl installation or source tree... not found checking dune/istl/istlexception.hh usability... no checking dune/istl/istlexception.hh presence... no checking for dune/istl/istlexception.hh... no configure: dune-istl does not provide libs checking for dune-foo installation or source tree... found in /usr/people/robertk/disk1/Dune/trunk/install/dune-foo-0.1 checking dune/foo/foo.hh usability... yes checking dune/foo/foo.hh presence... yes checking for dune/foo/foo.hh... yes configure: dune-foo does not provide libs configure: error: could not find required module dune-istl --- Failed to build dune-bar --- Terminating dunecontrol due to previous errors!