#1156 Unexpected behavior of the build system when haveing worng defined modules
Metadata
Property | Value |
---|---|
Reported by | Tobias Malkmus (tomalk@mathematik.uni-freiburg.de) |
Reported at | Jul 19, 2012 09:16 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Last edited at | Feb 1, 2013 01:49 |
Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
Closed at | Feb 1, 2013 01:49 |
Closed in version | Unknown |
Resolution | Fixed |
Comment | Commited my patch as r7097. |
Description
I don't know wether its a bug or not.
Additional modules, which have wrong m4 scripts and are not in the dependes or sugestion list, can have impact on the build process.
Lets have a look at this situation: You have a acctual svn checkout of dune-common. Also there are three additional modules ( dune-a, dune-b and dune-c) which all depend on dune-common.
dune-a will be the working module an has a suggestion on dune-c.
In the m4 script of module dune-b a small error is added ( e.g. due to copying of moduls). The m4 check for module dune-b is
AC_DEFUN([DUNE_C_CHECK_MODULE],[...])
instead of
AC_DEFUN([DUNE_B_CHECK_MODULE],[...])
( I know it is wrong )
While trying to build dune-a using
./dune-common/bin/dunecontrol --module=dune-a all
the m4 test for dune-c fails. ( see attached log )
If dune-b and dune-c are chaned by their names this error does not occur. So it seems to me that this error is module name dependent.