#1351 dunecontrol enforces dependencies of modules that are not being built
Metadata
Property | Value |
---|---|
Reported by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Reported at | Sep 10, 2013 09:57 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Last edited at | Sep 10, 2013 10:07 |
Closed by | Steffen Müthing (steffen.muething@iwr.uni-heidelberg.de) |
Closed at | Sep 10, 2013 10:07 |
Closed in version | Unknown |
Resolution | Duplicate |
Comment | Sorry for the noise, this is a duplicate of FS1343. |
Thanks for the heads-up, Christoph! |
Description
When you run dunecontrol with --module=dune-xxx or --only=dune-xxx I would expect its module dependency resolution to only consider module dependencies that are listed as dependencies of dune-xxx (--only) or that are flagged for rebuilding (--module). But dunecontrol requires all module dependencies to be met. Example:
[muethisn@dhcppar3 dune (master *)]$ ls dune-common dune-grid [muethisn@dhcppar3 dune (master *)]$ dune-common/bin/dunecontrol --only=dune-common autogen --- going to build dune-common --- --- calling autogen for dune-common --- ERROR: could not find module dune-geometry, module is also unknown to pkg-config. Maybe you need to adjust PKG_CONFIG_PATH! dune-geometry is required by dune-grid --- Failed to build dune-common --- Terminating dunecontrol due to previous errors! [muethisn@dhcppar3 dune (master *)]$
Is that a bug or a feature? ;-) In any case, it is confusing… I think that dunecontrol should only consider the dependencies of those modules that are being built.